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.
Most of the documents I translate are Polish->English/Russian. I have huge glossaries, first created in xls and then converted into txt.
The problem is: Omega T finds words in my glossary ONLY if they're in the same grammatical case (nomin., accusa. etc.). In Polish the same word ends with ending when used in different grammatical cases.
I know it has already been discussed at some polish forums, but no solution has be... See more
OmegaT v 3.6.0_11
Most of the documents I translate are Polish->English/Russian. I have huge glossaries, first created in xls and then converted into txt.
The problem is: Omega T finds words in my glossary ONLY if they're in the same grammatical case (nomin., accusa. etc.). In Polish the same word ends with ending when used in different grammatical cases.
I know it has already been discussed at some polish forums, but no solution has been found.
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Susan Welsh United States Local time: 01:30 Russian to English + ...
recognition of declensions
Apr 25, 2019
I'm not an expert, but I do not have this problem with Russian declensions. OmegaT recognizes them almost perfectly. I suggest that you upgrade to the latest build: OmegaT 4.2.0. The older versions of the software required the attachment of Tokenizers to recognize declined forms, but this is no longer necessary.
If that doesn't work and nobody else answers here, ask on the Yahoo group... See more
I'm not an expert, but I do not have this problem with Russian declensions. OmegaT recognizes them almost perfectly. I suggest that you upgrade to the latest build: OmegaT 4.2.0. The older versions of the software required the attachment of Tokenizers to recognize declined forms, but this is no longer necessary.
Unfortunately OmegaT 4.2.0 has the same problem - I have installed it today. I read at another OmegaT forum that the program has got no problem with Russwian or Czech declension, because of a plugin that somebody wrote to solve it. I'm trying to figure if there's any "plugin" or anything that would help with Polish declension.
Thank you for the yahoo link, I'll ask there also.
Aleksandra
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
esperantisto Local time: 08:30 Member (2006) English to Russian + ...
SITE LOCALIZER
Tokenizers
Apr 25, 2019
Tokenizers are the answer. For some languages, dedicated tokenizers are available. If Polish is not among them, tokenization can be done using the respective Hunspell dictionary. Thus, check the project properties for the tokenizer enabled for your target language.
DZiW (X)
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
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.