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


Op Wo, 2012-07-11 om 11:01 -0400 skryf Chris Leonard:
On Tue, Jul 10, 2012 at 2:37 AM, Rimas Kudelis <rq@akl.lt> wrote:

I believe there have been thoughts about migrating to gettext properly, but
considering the amount of work it would take and the impact, no wonder it
hasn't happened (or perhaps even started) yet.

Rimas

Thanks for the answer Rimas.  I do understand the challenges of
working solely in gettext with a project as large and diverse as
LibreOffice.

It is nonetheless unfortunate that it is necessary to hack the msgctxt
comment to achieve your L10n.  Not so much for the extra burden it
places on localizers, which can largely be mitigated by working in
Virtaal with it's translation memory (for instance); but for it's
impact on other string comparison tools like Translate Toolkit.

Sounds good, except that using msgctxt like this for OOo/LibO
localisation was invented by us in the Translate Toolkit :-)

When running oo2po, you can specify if you want to use msgctxt like
this, or to merge in the traditional gettext way:
http://translate.sourceforge.net/wiki/toolkit/duplicates_duplicatestyle

The idea is to make it possible to translate things differently if
needed. If things are merged, it is not possible, while the code base
supports it.

I came across this during a process of doing cross-project consistency
checks for conflicting translations.  I'm a scientist by training and
data pipelining quality checks is just one of those things I feel
compelled to do. I realized that one of my usual tricks was less
effective than it usually is, however, it still yields some useful
results.

This sounds similar to what poconflicts do, or did I misread it? I think
poconflicts should ignore the msgctxt as you want, but maybe I'm
misundererstanding what you are trying to do.

Friedel

-- 
Recently on my blog:
http://translate.org.za/blogs/friedel/en/content/localisation-guide-now-available-spanish


-- 
Unsubscribe instructions: E-mail to l10n+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

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.