This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
TM entries with almost-matching locales can now be shown as fuzzy matches with a configurable penalty.
The bundled JRE in "with-JRE" distributions has been updated to Java 8u222, now from AdoptOpenJDK rather than Oracle. Note that the 32-bit Linux distribution has been discontinued. 32-bit Linux users should use the "without-JRE" distribution and supply their own JRE.
Regex search-and-replace results were incorrect for some replacements.
The Basque, Brazilian Portuguese, Czech, Dutch, French, Italian, Russian, Simplified Chinese, and Ukrainian localisations were updated.
The OmegaT Project always welcomes developers, localisers and users to contribute their experience, knowledge and insights to the software we release.
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Samuel Murray Netherlands Local time: 01:52 Member (2006) English to Afrikaans + ...
Yes
Oct 11, 2019
Susan Welsh wrote: BCP 47 language tags are now supported.
FWIW, these language "tags" are what we usually call language "codes", although the BCP47 project refers to them as "tags". I'm not sure how this would work in practice, because wouldn't using these in TMX files make the TMX files non-compliant?
The bundled JRE in "with-JRE" distributions has been updated to Java 8u222, now from AdoptOpenJDK rather than Oracle.
This has the effect of causing some plugins to stop working (e.g. the browser plugin), and when that happens, OmegaT throws an error when you open it.
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Susan Welsh wrote: BCP 47 language tags are now supported.
FWIW, these language "tags" are what we usually call language "codes", although the BCP47 project refers to them as "tags". I'm not sure how this would work in practice, because wouldn't using these in TMX files make the TMX files non-compliant?
Language codes in TMX files must comply with BCP47. If a language code in a TMX file is not valid BCP47 code, the TMX file is not valid.
Rodolfo M. Raya
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Create your account in minutes, and start working! 3-month trial for agencies, and free for freelancers!
The system lets you keep client/vendor database, with contacts and rates, manage projects and assign jobs to vendors, issue invoices, track payments, store and manage project files, generate business reports on turnover profit per client/manager etc.
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.