Ian Jackson wrote:
[just answering one of your questions]
6. Committing the .pot file
You can't expect translators to be ready to run any commands (or even to
have the required tools installed) to generate the .pot file(s).
But it is still (in my opinion) a bad idea to commit the .pot file.
Frans Pop wrote:
While uploading a package with your translation update in
it, I noticed some error messages. After checking, I saw
that your translation update contained a lot of "\n"
(newline) instead of spaces at the end of lines.
I have corrected these errors in the D-I da.po files.
I
Clytie Siddall wrote:
I would prefer a translated page-name, but
I haven't seen UTF-8 wiki URLs yet, so in Vietnamese, we get dreadfully
messy-looking URLs like this:
http://wiki.services.openoffice.org/wiki/C%C3%A1ch_d%E1%BB%8Bch
The pagename is simply:
Cách dch
or "how to translate".
Matthias Julius wrote:
Couldn't dh_installman do that? (Well, not the reviewing
part.) Many Encodings can be autodetected. And for those
that can't it could give an error forcing the maintainer
to specify an encoding as command line option.
Some simple spell-checking might work as an encodi
Christian Pernegger wrote:
You seem to assume here that only users who don't speak
English like i18n'ed software. That's untrue. I do use a
fully localized system and I tend to think that I speak a
quite decent English.
Mmm, same here. Still, I don't like it half-and-half - having to
produce
Martijn van Oosterhout wrote:
On 8/21/06, Jacob Sparre Andersen <[EMAIL PROTECTED]> wrote:
Would it be possible to add a comment field per package
translation in DDTSS?
Sounds like a good idea, what were you thinking? A
free-form field after the translation where anything could
be
Would it be possible to add a comment field per package
translation in DDTSS?
Last night I and some other Danish translators ended up
discussing translation policy in the actual translation
fields in DDTSS, rather than in a comment field (as we
should).
When a reviewer makes a change to a t
ssage ---
On Wed, 2006-06-07 at 10:20:44 +0300, Guillem Jover wrote:
> On Tue, 2004-01-27 at 18:13:35 +0100, Jacob Sparre Andersen wrote:
> > Package: dpkg
> > Version: 1.9.21
> > Severity: important
> >
> > It appears that the codes in the first two (three?) columns
Denis Barbier wrote:
Miroslav Kure wrote:
Unfortunately, nonbreakable space is not included in
character class \s or [:space:] (aka whitespace). As it
is usually not distinguishable from the ordinary space in
most of the fonts, I would say that nonbreakable space
should be added to the whit
Denis Barbier wrote:
At the moment, only one sorting order is allowed for all
materials, and fixing that may be quite hard,
http://people.debian.org/~barbier/intl/l10n/unstable/ If
you prefer this sorting order, I will grab by_vote instead
of by_inst, please have a look and let me know.
I
Claus Hindsgaul wrote:
But how about the program translations? One could argue
that it would make more sense to sort/prioritize the
translations after how often a program is executed, since
that would be an approximate measure of how often the
translation is shown to a user.
What do you th
Christian Perrier wrote:
That is a common feature of XLIFF/TMX editors: fuzzy
matching on present translation memories.
What a great featureand, for sure, XLIFF editors are
the only tools to have it.
I may misremember completely, but I am almost certain KBabel
had this feature four or
Nicolas François wrote:
[EMAIL PROTECTED] wrote:
So, is this correct or are these man pages wrong?
IMHO, it should be translated...at least for some
languages.
Here is an extract from the lexgrog.l file:
===
[...]
H
Christian Perrier wrote:
Many translated man pages indeed have translated the
"NAME" section name...which confuses lexgrog.
So, is this correct or are these man pages wrong?
I guess the same stands for DESCRIPTION, SYNOPSIS, SEE
ALSO, etc.
I suppose that we agree that the user should be sh
Felipe Augusto van de Wiel wrote:
> #: src/cmdline/cmdline_resolver.cc:630
> msgid "Invalid response; please enter 'y' or 'n'."
> msgstr "Resposta inválida : por favor informe 'y' ou 'n'."
>
> My question is: "could we translate the y and n"?
My suggestion is that you report this as an "i18n bug
Christian Mack wrote:
> Frans Pop wrote:
> > We have already decided in the past that we would follow
> > US spelling.
>
> Perhaps this decision should be part of the policy?
> Or at least be mentioned on the i18n documentation?
Agreed.
Jacob
--
"Can we feel bad for the universe later?"
--
Jean Christophe André wrote:
> Eddy Petrior a écrit :
> > Either way, there should be a bug against
> > "debian-policy". Is there an interest in this issue at
> > the moment?
>
> Yes!
Ditto.
> > proposal: /etc/default/environment
>
> My proposal: /etc/default/i18n
Using "/etc/default/i18n" (
Christian Perrier wrote:
> http://people.debian.org/~bubulle/d-i/i18n-doc/languages.xml
Thanks for this nice overview.
I noticed that Faroese (fo) is completely missing from the
list although there at least is a partial Faroese locale
included in Debian.
> You currently need a fully XML/XSL cap
Ian Jackson wrote:
> As a good rule of thumb, there is no point translating an
> incomprehensible English message :-).
Agreed!
Preferably it shouldn't show up in the POT files either.
Jacob
--
»When in Rome; burn it«-- Diziet Sma
--
To UNSUBSCRIBE, email to [EMAIL PR
Ian Jackson wrote:
> You seem to be suggesting removing the detail from dpkg's
> error handling - ie, reporting less information to make
> the translation easier.
Removing information from the error messages is generally a
bad idea, BUT it is also a waste of everybody's time to put
strings which
Eddy Petriºor wrote:
> Scott James Remnant wrote:
> > > Denis Barbier wrote:
> > > > Scott James Remnant wrote:
> > > > > Yes, because god forbid a developer should be able
> > > > > to understand what's going on when a user files a
> > > > > bug report.
> > > >
> > > > These ohshite messages tell
Christian Perrier wrote:
> > The text is displayed to the user as a list of timezones
> > in their country, from which they choose their timezone.
> > That's all it should be. The comments tell you to
> > translate the English text and they give the English
> > text. You are not supposed to transl
Eddy Petrisor wrote:
> The support is there, but the original phrasing makes the feature
> useless; As I said:> > > > > > Thus, the string
> > > "unhold: upgrade or leave uninstalled" is ambiguous (in
> how many are uninstalled?
Wouldn't
printf(ngettext("unhold: upgrade or leave uninstalled
Eddy Petrisor wrote:
> 2) in some languages forms like "3 installed packages", "1
> installed package" and "6 installed packages" need three
> different forms for the word "installed". Thus, the string
> "unhold: upgrade or leave uninstalled" is ambiguous (in
> this case might not be the case - I
Scott James Remnant wrote:
> I think it's important that the English messages in dpkg
> be good, clear English.
I agree with you on that, but I would like to remind you
that the message-ids technically are POSIX/C and not
English.
> I do not believe that this should be sacrificed for the
> sake
On Tue, 14 Jun 2005, Luk Claes wrote:
> On Tue, 14 Jun 2005, Jacob Sparre Andersen wrote:
> > That's definitely a good idea. Translators also have
> > the additional benefit of knowing what kind of extra
> > context actually is important to make translation
> >
On Tue, 14 Jun 2005, Scott James Remnant wrote:
> On Tue, 2005-06-14 at 10:06 +0200, Luk Claes wrote:
> > One can include the comments in the source files (a
> > rather recent post on d-i18n gave the required syntax),
> > then they can appear as automatic comments in the pot
> > file.
>
> This so
Giuseppe Sacco skrivaði:
> Il giorno dom, 01-05-2005 alle 14:50 +0200, Jacob Sparre
> Andersen ha scritto:
> > a) Most maintainers know less than 10 languages. And
> > Debian is distributed in (more than?) 30 languages.
> > This gives (as a very rough estimate)
Keld Jørn Simonsen skrev:
> Jacob Sparre Andersen wrote:
> > The maintainer should _never_ get bug-reports in other
> > languages than English. (at least not in that role)
>
> Why not? Many developers know other languages than
> English, and are able to deal w
Giuseppe Sacco ha scritto:
> Il giorno sab, 30-04-2005 alle 13:39 +0200, Jacob Sparre
> Andersen ha scritto:
> > The maintainer should _never_ get bug-reports in other
> > languages than English. (at least not in that role)
>
> I think this may be the simplest soluti
Keld Jørn Simonsen wrote:
> Jutta Wrage wrote:
A part of the effectiveness of the Open Source community is
how we do massively parallel testing. If we move the task
of checking if an error in a program is already known from
the testers to the developers, then this system breaks. So
we have to ke
Ruben Porras wrote:
> El lun, 25-04-2005 a las 14:04 +0200, Jacob Sparre Andersen escribió:
> > Wouldn't it be better, if the strings _showing_ the
> > choices were excluded from the .pot msgids? That way
> > there wouldn't be so much doubt - and less risk o
Clytie Siddall wrote:
> Eugeniy Meshcheryakov wrote:
> >> I've translated "Yes" and "No" separately in this file,
> >> but I haven't yet seen a translation for Y and n. Does
> >> this mean I should not translate this to the equivalent
> >> in my language? [C/k]
> >
> > It looks like aptitude expec
Miroslav Kure wrote:
[ are you on debian-i18n, or would you like to be Cc'ed? ]
> After the fresh install of Sarge in Czech language you end
> up with system where (almost) everything is localised to
> Czech and you can read/write iso-8859-2 characters.
>
> % cat /etc/environment
> LANGUAGE="cs_
Konstantinos Margaritis wrote:
> 2) If debian-installer/keymap is not set or if its value
> is not in the map, the script will try to fall back to the
> previous method of checking the locale but with a
> difference. This time, it will try to be intelligent and
> if a locale entry is not in the li
Renato Serodio wrote:
> I'm a Debian user, Portuguese by nationality, living in
> Germany, working and coding in English, speaking
> additionally Russian.
>
> Now, I keep everything in the system in English, without
> special characters of any kind. I want, nonetheless, to be
> able to read and w
On Sun, 9 Jan 2005, Martin Zobel-Helas wrote:
> On Sunday, 09 Jan 2005, you wrote:
> > What is the non-free part of latex-beamer?
> no, but you need Adobe Acrobat Reader.
It doesn't work with xpdf?
Jacob
--
»By becoming continuous, war has fundamentally changed its character.
In past ages, a
Marc Haber wrote:
> Usually, I am not impressed by the translations because
> they usually feel clumsy and awkward to me, as if I were
> explaining the things to a child. Strangely, most German
> translations of commercial software doesn't sound that
> clumsy - probably because I don't know the en
Marco d'Itri wrote:
> Christian Perrier wrote:
> > Some of you guys take care of them...and after a few
> > days upload a new version with the updated templates.
> > Thanks to you, you're by chance the majority.
>
> I do not think this is a good thing. Packages with updated
> templates should be u
Thiemo Seufer wrote:
> Which means you have to beg the upstream author to change
> to output of his program without apparent reason (for
> him). Why should he care about some random other program
> which happens to use the same string in a different
> context?
If it is a different program and in
Nikolai Prokoschenko wrote:
> Could someone remind me, what is needed to provide plural
> forms in an app?
It should mostly be covered in this chapter of the GNU
Gettext manual:
http://www.gnu.org/software/gettext/manual/html_chapter/gettext_10.html
The basic trick is to use the function "n
Preben Randhol wrote:
> Looking at this page:
>
> http://www.debian.org/international/l10n/po/no
>
> There is even more stupidity as it has:
>
>[nb] [nn] [no] [no_NO] [no_NY]
The last one looks mostly like a mistyping of "nn_NO" to me.
There is apparently only one file and a fe
Preben Randhol wrote:
> Carlos Perelló Marín wrote:
> > With bash:
> >
> > export LANGUAGE=no_NO:no_NY:nb:nn
>
> Thanks, but I have tried this and it doesn't work.
I have tried it too (with "fo_FO:fo:da_DK:da). And it
appears to work with some programs (rpm, gettext, find).
But it is definit
Preben Randhol wrote:
> Tobias Toedter wrote:
> Yes, but there must be a better way to get a change
> throughout Debian than to have to do a bugreport to every
> package. What I need is to establish that nb_NO and nn_NO
> are the official names and then I might go to the DWN to
> get teh message o
Tobias Toedter wrote:
> I don't know any Norwegian at all, so just out of
> curiosity: what is the difference between the two
> languages? Why should the locale be set to Bokmål instead
> of Nynorsk?
Nynorsk (New Norwegian) is somewhat similar to the ancient
Nordic language and to Icelandic and
Preben Randhol wrote:
> There are two Norwegian languages; bokmaal and nynorsk.
> Translations are done for both. Bokmaal is the nb_NO and
> nynorsk is nn_NO. The problem is that many programs (such
> as gnumeric) uses the old no_NO and not nb_NO for bokmaal.
> This leads to problems when one sets
Dominique Devriese wrote:
> CURRENT KDE SYSTEM
[...]
> A user only installs one translation package ( for his
> language of course ) ( or more if he wants more
> languages, of course ).
> PROPOSED DEBIAN SYSTEM
[...]
> 2. The translators don't try to get their work
>included in
Martin Quinson wrote:
> I repost this because I got no feedback at all. I guess it
> shows that my email was long enough for not being read :)
You seem to have the same misunderstanding as one of my old
math professors. No response often (and IMHO also in this
case) means that things are quite f
Marcin Owsiany wrote:
> On Fri, May 16, 2003 at 10:28:25AM +0200, Martin Quinson wrote:
> [...]
> > As long as dpkg isn't patched, the two only solutions
> > are to put translated manpages within the binary
> > packages, or in a catch-all package.
>
> I think we should do the former, since it will
Denis Barbier wrote:
> There is currently no consensus whether translated man
> pages should be shipped along with original man pages or
> within manpages-xx packages.
Personally, I would prefer that translations (of both
man-pages and user-interface) were shipped in separate
packages on a per pa
50 matches
Mail list logo
