Hello Clytie,
Thanks for the forward. You know I cannot read so many mailing lists :-)
Hello Adam,
> > I need to be able to call
> > [d[c]]pgettext(), as described in the gettext manual[1].
> >
> > Despite having all the gettext-related packages that I can find
> > installed on my system, these
MJ Ray asked:
> > Question raised on -l10n-esperanto recently: can gettext be used for
> > localising a program with a utf-8 non-English source language?
> > That is, the thing in the _("...") has accents and isn't English.
Technically, it is possible to use a non-English source language.
You h
Christian Rose wrote:
> gettext's English-centredness (which to large parts is historical, but
> in some cases still exists, like in the handling of plural forms) is
> both a blessing for our community where English is the UI default, as
> much as it is a nuisance in other real-life software develo
Clytie,
> It's great to know gettext can already do this: it means we can start
> testing the process.
>
> This facility is needed for the cases when translating from a non-
> English language _would_ produce a better result.
>
> For my language alone, there are many possible translators who
F Wolff wrote:
> > What you call "gettext's English-centredness" is only a recommendation
> > in the doc. You _can_ use another language as the language of the source
> > files and the msgids in the PO files. Did you try it? Did you encounter
> > problems?
>
> Well, I did not try it, but the examp
Jean-Christophe Helary wrote:
> In the next decades and starting very soon, the world's most
> understood languages will be Chinese and Hindi, and especially those
> two will have a huge influence on the IT world. And only the people
> who don't read Chinese on Hindi are blind to that.
>
> I
Hello Clytie,
> Another translator has
> already mentioned doing this in Emacs: keeping the backup language PO
> file as a reference. So if we could request:
>
> msgid[en]
> msgid[xx]
> msgstr
>
> in an editor, specifying the secondary msgid language in the prefs, ...
It can not be done pur
Hi Danilo,
> > The syntax for a mixed PO file could like this:
> >
> > msgid "Hello, world!"
> > msgid[ru] "Здравствуй, мир!"
> > msgstr "Chào thế giới !"
>
> I think the following would make more sense (except that the syntax
> would conflict plural forms syntax):
>
>msgid "Hello, wor
Dwayne Bailey wrote:
> > The syntax for a mixed PO file could like this:
> >
> > msgid "Hello, world!"
> > msgid[ru] "Здравствуй, мир!"
> > msgstr "Chào thế giới !"
>
> these are the issues I see:
>
> * Plurals - mentioned already
I can reduce the number of plural forms to 2, by choosing
Eddy Petrișor wrote:
> > In our example,
> >
> > msgid "Hello, world!"
> > msgid[ru] "Здравствуй, мир!"
> > msgstr "Chào thế giới !"
> >
> > can become
> >
> > #, fuzzy
> > #| msgid "Hello, world!"
> > msgid "Hello, the entire world!"
> > msgid[ru] "Здравствуй, мир!"
> > msgstr "
Dwayne Bailey wrote:
> > I can reduce the number of plural forms to 2, by choosing for the
> > "singular" the one with n = 1 and for "plural" the one which is chosen
> > most often for n -> ∞.
>
> Would it not be a better options to have
>
> msgid[0][ru]
> msgid[1][ru]
> etc
>
> So that the prop
Clytie Siddall wrote:
> > The translator then only needs to compare the previous and the current
> > msgid ("too many arguments" and "too few arguments"), and infer which
> > parts of the translation she needs to change."
>
> This is great. :)
>
> Thanks, Bruno!
>
> Now I just need to talk
Hello Amos,
> You can download it:
> http://www.runasimipi.org/instrans.zip
>
> See the documentation for the scipt at:
> http://www.runasimipi.org/instrans-en.html
Thank you for making this available. Yesterday I looked at it, but am a
bit confused about the purpose of some features, and theref
Hello,
Clytie Siddall wrote:
> msgctxt is a formal context field, e.g.
>
> msgctxt "This is a button: keep it short"
> msgid "Convert"
> msgstr "Đổi"
>
> It's an innovation we've needed badly for a long time, but until
> enough people and servers are running gettext 0.15, we can't use it. :(
>
e contains this:
"Project-Id-Version: iso_639 CVS\n"
...
"Last-Translator: Bruno Haible <[EMAIL PROTECTED]>\n"
But I am not and was never a translator for the isoqlog package. I'm only
a translator for the iso_639 domain. The German translator for isoqlog must
be someone el
Christian Perrier wrote:
> > 1) Someone has apparently merged parts of iso_639.pot into the isoqlog.pot
> >file. This is a *bad* thing, because it causes translators to do
> > duplicated
>
>
> I don't think that this is what happened. More likely did the german
> translator use something lik
Jens Seidel wrote:
> You still have a lot to do, only 4% are translated: 358t;3827f;3417u
This is a mistaken perception: The iso-639-3 (note the -3 !) file contains
lots of proper names which are the same in English and German. "Lingala",
"Matengo" and many others are just the same in both languag
Clytie Siddall wrote:
> I'm a little confused about which file is "iso-639-3". I translate
> the iso-codes package for Debian and the TP, and it doesn't list such
> a file. The listing (ver. 0.55) is:
>
> iso_3166 country names 410 strings
> iso_3166_2
Alastair McKinstry wrote:
> whats the best way for gettext to handle strings that are unlikely to be
> translated / need to be translated? These files contain lots of such
> strings, that the translator will probably review and decide do not
> need translating. Two solutions come to mind:
> - tools
19 matches
Mail list logo
