You can download the latest build in the Download section at We’re happy to announce that we have put in place a special promotion until Septemfor GALA members. This build also adds a few more enhancements and fixes. Current UTX users do not need to do anything with their current Xbench projects, their files will simply be shown more conveniently. utx extension, presents banned terms more evidently and does not show UTX commented out lines. With this build, we made the tab-delimited filter smarter and now it accepts files with. It is so simple that, in fact, UTX users are already loading their glossaries into Xbench as tab-delimited files and everything works, except for a few minor quirks. UTX is a very simple tab-delimited terminology format.
#ADD XLIF FILE TO XBENCH SOFTWARE#
We do encourage software developers to add support for these new formats to capitalize on the synergies for users and developers that exist when formats are documented and designed with interoperability in mind. Alternatively, you can also load an XLIFF:doc file directly with the XLIFF file type and Xbench will recognize the dialect. With this new Xbench 3.0 build, you can now load a TIPP file directly and search or QA the XLIFF bilingual information it contains. As any standard becomes meaningful only if users can actually benefit from it, we decided to jump in quickly and add support for these formats in Xbench to help foster adoption in real-life workflows.
A few weeks ago, the Interperability Now! initiative reached an important milestone: it released the specification for TIPP 1.0 and XLIFF:doc 1.5, which was the first official release of this new set of conventions. For now, we will focus on the mainstream protocols (http:, https:, ftp:, file:, mailto:) to reduce the risk of false alarms, although the protocol list will grow in the future.Although some portions of URLs are case-insensitive and other portions are case-sensitive, we think that it is good translation practice not to change the URL case, so we decided to flag uppercase/lowercase mismatches as well. We’ve made a couple of practical design decisions: With this new build, we decided to simplify that by adding a built-in QA check for URL mismatches. Actually, every now and then our support team helped users to add the URL check into a checklist. Although, it is true that you can already use the Xbench powerful checklist feature to catch URL mismatches (very typically created by improper handling of fuzzy matches), it is also true that mastering regular expressions and the Xbench PowerSearch grammar to create such a check is not trivial to everyone. We’re happy to announce that we’ve just published build Xbench 3.0 build 1148.
0 kommentar(er)
