Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


2011.03.04 10:09, Yury Tarasievich rašė:
On 03/04/2011 09:40 AM, Dwayne Bailey wrote:

On 2011-03-04 09:14, Yury Tarasievich wrote:
...
description of the .PO based L10N process. Pootle isn't acceptable for
the languages with the comparatively weak terminological base . In
such cases it's common for everybody to translate "just as one sees
...
We have many African languages who also have weak terminology that
benefit from using Pootle.

The difference is that they include their terminology in the terminology
project on Pootle. You can do that also, in which case people giving
suggestions and translations are guided by the teams terminology lists.

The big problem is this procedure isn't well visible or integrated. E.g., one may easily bypass it or ignore it. Also, the terminology matching isn't as quite clear-cut process as many tools make it to look (Pootle, too, as far as I can understand -- I know Pootle only superficially). E.g., is there a support for the context variants (translate as A1 in context C1, as A2 in C2 etc.)?

Yury,

Pootle does not check your translation against terminology. It's the other way around: it suggests terms from the terminology when you do the translation.

Rimas


--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.