gnupdate-i18n — Internationalization and translation

Re: [GNUpdate-i18n] Update libpackman Dutch translation

[Christian H. <ch...@gn...>]

On Mon, Oct 07, 2002 at 02:28:09PM +0200, Bert De Meyer wrote:
> Christian,
> 
> can you commit this ?
> 
> cya,
> 
> Bert

Yep. Committed.

Christian

-- 
Christian Hammond         <>  The GNUpdate Project
ch...@gn...      <>  http://www.gnupdate.org/
   "We anticipate a global world-market with place for perhaps five computers."
      -- Tom Watson, IBM 1949

Re: [GNUpdate-i18n] Update libpackman Dutch translation

[Bert De M. <BD...@Di...>]

Christian,

can you commit this ?

cya,

Bert

On Sun, 2002-10-06 at 16:25, Bert De Meyer wrote:
> Applied the changes,
> 
> Bert
> 
> On Sat, 2002-10-05 at 20:20, Gerhard Muntingh wrote:
> > On Sat, Oct 05, 2002 at 01:17:47PM +0200, Bert De Meyer wrote:
> > > Updated version !
> > > Gerard,can you verify this maybe ?
> > 
> > Sure, I have a few minor remarks.
> > I'd use `regel' instead of `lijn'.
> > 
> > > #: libpackman/module.c:168
> > > #, c-format
> > > msgid "Failed to load module %s: %s\n"
> > > msgstr "Het openen van module %s is mislukt: %s\n"
> > > 
> > > #: libpackman/module.c:216
> > > #, c-format
> > > msgid "Failed to close module: %s\n"
> > > msgstr "Het sluiten van module: %s is mislukt\n"
> > 
> > Keep consistent with opening.  So:
> > "Het sluiten van module %s is mislukt\n"
> > 
> > > #: libpackman/package.c:44
> > > #, c-format
> > > msgid ""
> > > "NULL filename in __fileHashKey in %s, line %d. Report this to the "
> > > "developers.\n"
> > > msgstr ""
> > > "NULL filenaam in __fileHashKey in %s,lijn %d. Gelieve dit te melden aan de developers.\n"
> > 
> > "NULL bestandsnaam in __fileHashKey in %s, regel %d. Gelieve dit te melden aan de developers.\n"
> > 
> > > #: modules/database/gnupdate/db/db.c:224
> > > msgid ""
> > > "GNUpdate DB: Possible database corruption! Back up your database and contact "
> > > "a developer.\n"
> > > msgstr ""
> > > "GNUpdate DB:Mogelijke database corruptie!\n"
> > > "Maak een backup van uw database contacteer een developer\n"
> > 
> > "Maak een backup van uw database en neem contact op met een developer\n"
> > 
> > > #: modules/package/rpm/rpm.c:319
> > > msgid "Old format source packages cannot be queried.\n"
> > > msgstr "Het formaat van oude source packages kan niet worden geverifie?rd.\n"
> > 
> > msgstr "Het formaat van oude source packages kan niet worden opgevraagd.\n"
> > 
> > 
> > regards,
> > 
> > Gerhard.
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > GNUpdate-i18n mailing list
> > GNU...@li...
> > https://lists.sourceforge.net/lists/listinfo/gnupdate-i18n
> > 
> 
> ----
> 

> # SOME DESCRIPTIVE TITLE.
> # Copyright (C) 2002 Free Software Foundation, Inc.
> # Gerhard C. Muntingh <ger...@mu...>, 2002.
> #
> msgid ""
> msgstr ""
> "Project-Id-Version: PACKAGE VERSION\n"
> "POT-Creation-Date: 2002-06-26 20:11-0700\n"
> "PO-Revision-Date: 2002-10-05 23:40+0200\n"
> "Last-Translator: Bert De Meyer <bd...@di...>\n"
> "Language-Team: Netherlands <nl...@li...>\n"
> "MIME-Version: 1.0\n"
> "Content-Type: text/plain; charset=CHARSET\n"
> "Content-Transfer-Encoding: 8bit\n"
> #: libpackman/internal.c:174
> #, c-format
> msgid "libpackman: __getEnvInfo(): No such user %d."
> msgstr "libpackman: __getEnvInfo(): De gebruiker %d bestaat niet."
> 
> #: libpackman/internal.c:181
> #, c-format
> msgid "libpackman: __getEnvInfo(): %s."
> msgstr "libpackman: __getEnvInfo(): %s."
> 
> #: libpackman/module.c:138
> #, c-format
> msgid "Failed to initialize libltdl: %s\n"
> msgstr "Het initialiseren van ltdl is mislukt: %s\n"
> 
> #: libpackman/module.c:168
> #, c-format
> msgid "Failed to load module %s: %s\n"
> msgstr "Het openen van module %s is mislukt: %s\n"
> 
> #: libpackman/module.c:216
> #, c-format
> msgid "Failed to close module: %s\n"
> msgstr "Het sluiten van module %s is mislukt\n"
> 
> #: libpackman/package.c:44
> #, c-format
> msgid ""
> "NULL filename in __fileHashKey in %s, line %d. Report this to the "
> "developers.\n"
> msgstr ""
> "NULL filenaam in __fileHashKey in %s,regel %d. Gelieve dit te melden aan de developers.\n"
> 
> 
> #: modules/database/gnupdate/addpackage.c:48
> #: modules/database/gnupdate/addpackage.c:145
> #: modules/database/gnupdate/addpackage.c:236
> #, c-format
> msgid "GNUpdate DB: Unable to create Hash Table in %s, line %d\n"
> msgstr "GNUpdate DB: Kan geen hash tabel maken in %s, regel %d\n"
> 
> #: modules/database/gnupdate/addpackage.c:190
> #: modules/database/gnupdate/addpackage.c:281
> #, c-format
> msgid "GNUpdate DB: indexTree == NULL in %s, line %d\n"
> msgstr "GNUpdate DB: indexTree == NULL in %s, regel %d\n"
> 
> #: modules/database/gnupdate/addpackage.c:424
> #, c-format
> msgid "GNUpdate DB: Unable to add groups index tree in %s, line %d\n"
> msgstr "GNUpdate DB: Kan geen groep index tree toevoegen in %s, regel %d\n"
> 
> #: modules/database/gnupdate/get_dependencies.c:40
> #: modules/database/gnupdate/get_dependencies.c:117
> #, c-format
> msgid "GNUpdate DB: dbData == NULL. Unable to add reqDeps in %s, line %d\n"
> msgstr "GNUpdate DB: dbData == NULL. Kan geen reqdeps toevoegen in %s, regel %d\n"
> 
> #: modules/database/gnupdate/get_dependencies.c:60
> #, c-format
> msgid "GNUpdate DB: Unable to open reqdeps hashtable at %ld in %s, line %d\n"
> msgstr "GNUpdate DB: Kan de reqdeps hash tabel niet openen op %ld in %s, regel %d\n"
> 
> #: modules/database/gnupdate/get_dependencies.c:137
> #, c-format
> msgid "Unable to open reqdeps hashtable at %ld\n"
> msgstr "Kan de reqdeps hash tabel op %ld niet openen.\n"
> 
> #: modules/database/gnupdate/get_files.c:39
> #, c-format
> msgid "GNUpdate DB: dbData == NULL. Unable to add files in %s, line %d\n"
> msgstr "GNUpdate DB: dbData == NULL.Kan geen bestanden toevoegen in %s, regel %d\n"
> 
> #: modules/database/gnupdate/get_files.c:59
> #, c-format
> msgid "Unable to open file hashtable at %ld in %s, line %d\n"
> msgstr "Kan de file hash tabel op %ld niet openen in %s, regel %d\n"
> 
> #: modules/database/gnupdate/utils.c:97
> #, c-format
> msgid "GNUpdate DB: Unable to open package table at %ld in %s, line %d\n"
> msgstr "GNUpdate DB: Kan de package tabel op %ld in %s, regel %d niet openen\n"
> 
> #: modules/database/gnupdate/db/btree_header.c:179
> #, c-format
> msgid ""
> "GNUpdate DB: B+Tree: Unable to read the root node offset at %ld in %s, line %d\n"
> msgstr ""
> "GNUpdate DB: B+Tree: Kan de root node  offset op %ld in %s, regel %d niet lezen.\n"
> 
> #: modules/database/gnupdate/db/btree_header.c:208, c-format
> msgid "GNUpdate DB: B+Tree: Unable to read the left leaf offset at %ld in %s, line %d\n"
> msgstr "GNUpdate DB: B+Tree: Kan de linker leaf offset niet lezen op %ld in %s, regel %d\n"
> 
> #: modules/database/gnupdate/db/btree_header.c:237
> #, c-format
> 
> msgid "GNUpdate DB: B+Tree: Unable to read the tree size at offset (%ld) in %s, line %d\n"
> msgstr "GNUpdate DB: B+Tree: Kan de tree grootte niet lezen op offset (%ld) in %s, regel %d\n"
> 
> #: modules/database/gnupdate/db/btree_insert.c:240
> #, c-format
> msgid "GNUpdate DB: rootOffset = %ld in __insertKey('%s') in %s, line %d\n"
> msgstr ""
> msgid "GNUpdate DB: rootOffset = %ld in __insertKey('%s') in %s, regel %d\n"
> 
> #: modules/database/gnupdate/db/btree_node.c:268
> #: modules/database/gnupdate/db/db_blocks.c:138
> #, c-format
> msgid "GNUpdate DB: Dirty node at offset %ld has not been written to disk.\n"
> msgstr "GNUpdate DB: De dirty node op offset %ld is niet naar disk geschreven.\n"
> 
> #: modules/database/gnupdate/db/btree_traverse.c:142
> #, c-format
> msgid "GNUpdate DB: rootNode (%ld) is NULL in %s, line %d\n"
> msgstr "GNUpdate DB: rootNode (%ld) is NULL in %s, regel %d\n"
> 
> #: modules/database/gnupdate/db/db.c:57
> #, c-format
> msgid "GNUpdate DB: Unable to open database %s for reading.\n"
> msgstr "GNUpdate DB: Kan de database %s niet openen voor lezen.\n"
> 
> #: modules/database/gnupdate/db/db.c:116
> #, c-format
> msgid "GNUpdate DB: Unable to open database %s for reading/writing.\n"
> msgstr "GNUpdate DB: Kan de database %s niet openen voor lezen en schrijven.\n"
> 
> #: modules/database/gnupdate/db/db.c:224
> msgid ""
> "GNUpdate DB: Possible database corruption! Back up your database and contact "
> "a developer.\n"
> msgstr ""
> "GNUpdate DB:Mogelijke database corruptie!\n"
> "Maak een backup van uw database en neem contact op met een developer\n"
> 
> #: modules/database/gnupdate/db/db_blocklist.c:58
> msgid "GNUpdate DB: Truncated block list.\n"
> msgstr "GNUpdate DB: Er is een afgekapte block list.\n"
> 
> #: modules/database/gnupdate/db/db_blocks.c:279
> #, c-format
> msgid "GNUpdate DB: Unable to read block at %ld (%s) in %s, line %d\n"
> msgstr "GNUpdate DB: Kan block op %ld (%s) in %s, regel %d niet lezen.\n"
> 
> #: modules/database/gnupdate/db/db_blocks.c:308
> #, c-format
> msgid "GNUpdate DB: Unable to read %ld bytes from %s at offset %ld\n"
> msgstr "GNUpdate DB: Kan geen %ld bytes lezen van %s op offset %ld\n"
> 
> #: modules/database/gnupdate/db/db_blocks.c:341
> #, c-format
> msgid ""
> "GNUpdate DB: Infinite loop detected in database blocks in %s! Report this!\n"
> msgstr ""
> "GNUpdate DB: Oneindige lus gevonden in de database blocks in %s! Gelieve dit te melden !\n"
> 
> #: modules/database/gnupdate/db/db_blocks.c:413
> #, c-format
> msgid "GNUpdate DB: buffer == NULL in %s, line %d\n"
> msgstr "GNUpdate DB: buffer == NULL in %s, regel %d\n"
> 
> #: modules/database/gnupdate/db/db_header.c:39
> msgid "GNUpdate DB: Truncated database.\n"
> msgstr "GNUpdate DB: Afgekapte database.\n"
> 
> #: modules/database/gnupdate/db/db_header.c:48
> msgid "GNUpdate DB: Invalid database signature.\n"
> msgstr "GNUpdate DB: De database handtekening is ongeldig.\n"
> 
> #: modules/database/gnupdate/db/db_header.c:61
> #, c-format
> msgid "GNUpdate DB: Unsupported database version %d.%d\n"
> msgstr "GNUpdate DB: Deze database versie %d wordt niet ondersteund. %d\n"
> 
> #: modules/database/gnupdate/db/db_header.c:72
> msgid "GNUpdate DB: Unsupported database type.\n"
> msgstr "GNUpdate DB: Dit type database wordt niet ondersteund.\n"
> 
> #: modules/database/rpm/rpm.c:91
> msgid "Unsupported version of librpm.\n"
> msgstr "Deze versie van librpm wordt niet ondersteund.\n"
> 
> #: modules/database/rpm/rpm.c:673
> msgid "RPM DB: h == NULL. Unable to add files.\n"
> msgstr "RPM DB: h == NULL. Kan geen bestanden toevoegen.\n"
> 
> #: modules/database/rpm/rpm.c:760
> msgid "RPM DB: h == NULL. Unable to add required dependencies.\n"
> msgstr "RPM DB: h == NULL. Kan de benodigde dependencies niet toevoegen.\n"
> 
> #: modules/database/rpm/rpm.c:887
> msgid "RPM DB: h == NULL. Unable to add provided dependencies.\n"
> msgstr "RPM DB: h == NULL. Kan de geleverde dependencies niet toevoegen.\n"
> 
> #: modules/package/rpm/cpio.c:788
> #, c-format
> msgid "libpackman: rpm.so: can't rename %s to %s: %s\n"
> msgstr "libpackman: rpm.so: Kan %s niet naar %s hernoemen: %s\n"
> 
> #: modules/package/rpm/cpio.c:796
> #, c-format
> msgid "libpackman: rpm.so: can't unlink %s: %s\n"
> msgstr "libpackman: rpm.so: Kan %s niet verwijderen: %s\n"
> 
> #: modules/package/rpm/header.c:86
> #, c-format
> msgid "RPM: RPM_STRING_TYPE count must be 1 in %s, line %d\n"
> msgstr "RPM: RPM_STRING_TYPE count moet 1 zijn in %s, regel %d\n"
> 
> #: modules/package/rpm/header.c:138
> #, c-format
> msgid "RPM: Data type %d not supported in %s, line %d\n"
> msgstr "RPM: Data type %d wordt niet ondersteund in %s, regel %d\n"
> 
> #: modules/package/rpm/header.c:1378
> #, c-format
> msgid "RPM: Bad count for grpmHeaderAddEntry: %d\n"
> msgstr "RPM: grpmHeaderAddEntry is niet juist berekend: %d\n"
> 
> #: modules/package/rpm/lead.c:53
> msgid "RPM: Unable to read lead.\n"
> msgstr "RPM: Kan de 'lead' niet lezen.\n"
> 
> #: modules/package/rpm/rpm.c:221
> #, c-format
> msgid "RPM: File `%s' does not appear in the archive.\n"
> msgstr "RPM: File `%s' komt niet voor in de archive.\n"
> 
> #: modules/package/rpm/rpm.c:319
> msgid "Old format source packages cannot be queried.\n"
> msgstr "Het formaat van oude source packages kan niet worden opgevraagd.\n"

Re: [GNUpdate-i18n] Update libpackman Dutch translation

[Bert De M. <BD...@Di...>]

Applied the changes,

Bert

On Sat, 2002-10-05 at 20:20, Gerhard Muntingh wrote:
> On Sat, Oct 05, 2002 at 01:17:47PM +0200, Bert De Meyer wrote:
> > Updated version !
> > Gerard,can you verify this maybe ?
> 
> Sure, I have a few minor remarks.
> I'd use `regel' instead of `lijn'.
> 
> > #: libpackman/module.c:168
> > #, c-format
> > msgid "Failed to load module %s: %s\n"
> > msgstr "Het openen van module %s is mislukt: %s\n"
> > 
> > #: libpackman/module.c:216
> > #, c-format
> > msgid "Failed to close module: %s\n"
> > msgstr "Het sluiten van module: %s is mislukt\n"
> 
> Keep consistent with opening.  So:
> "Het sluiten van module %s is mislukt\n"
> 
> > #: libpackman/package.c:44
> > #, c-format
> > msgid ""
> > "NULL filename in __fileHashKey in %s, line %d. Report this to the "
> > "developers.\n"
> > msgstr ""
> > "NULL filenaam in __fileHashKey in %s,lijn %d. Gelieve dit te melden aan de developers.\n"
> 
> "NULL bestandsnaam in __fileHashKey in %s, regel %d. Gelieve dit te melden aan de developers.\n"
> 
> > #: modules/database/gnupdate/db/db.c:224
> > msgid ""
> > "GNUpdate DB: Possible database corruption! Back up your database and contact "
> > "a developer.\n"
> > msgstr ""
> > "GNUpdate DB:Mogelijke database corruptie!\n"
> > "Maak een backup van uw database contacteer een developer\n"
> 
> "Maak een backup van uw database en neem contact op met een developer\n"
> 
> > #: modules/package/rpm/rpm.c:319
> > msgid "Old format source packages cannot be queried.\n"
> > msgstr "Het formaat van oude source packages kan niet worden geverifie?rd.\n"
> 
> msgstr "Het formaat van oude source packages kan niet worden opgevraagd.\n"
> 
> 
> regards,
> 
> Gerhard.
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> GNUpdate-i18n mailing list
> GNU...@li...
> https://lists.sourceforge.net/lists/listinfo/gnupdate-i18n
> 

Re: [GNUpdate-i18n] Update libpackman Dutch translation

[Gerhard M. <ger...@mu...>]

On Sat, Oct 05, 2002 at 01:17:47PM +0200, Bert De Meyer wrote:
> Updated version !
> Gerard,can you verify this maybe ?

Sure, I have a few minor remarks.
I'd use `regel' instead of `lijn'.

> #: libpackman/module.c:168
> #, c-format
> msgid "Failed to load module %s: %s\n"
> msgstr "Het openen van module %s is mislukt: %s\n"
> 
> #: libpackman/module.c:216
> #, c-format
> msgid "Failed to close module: %s\n"
> msgstr "Het sluiten van module: %s is mislukt\n"

Keep consistent with opening.  So:
"Het sluiten van module %s is mislukt\n"

> #: libpackman/package.c:44
> #, c-format
> msgid ""
> "NULL filename in __fileHashKey in %s, line %d. Report this to the "
> "developers.\n"
> msgstr ""
> "NULL filenaam in __fileHashKey in %s,lijn %d. Gelieve dit te melden aan de developers.\n"

"NULL bestandsnaam in __fileHashKey in %s, regel %d. Gelieve dit te melden aan de developers.\n"

> #: modules/database/gnupdate/db/db.c:224
> msgid ""
> "GNUpdate DB: Possible database corruption! Back up your database and contact "
> "a developer.\n"
> msgstr ""
> "GNUpdate DB:Mogelijke database corruptie!\n"
> "Maak een backup van uw database contacteer een developer\n"

"Maak een backup van uw database en neem contact op met een developer\n"

> #: modules/package/rpm/rpm.c:319
> msgid "Old format source packages cannot be queried.\n"
> msgstr "Het formaat van oude source packages kan niet worden geverifie?rd.\n"

msgstr "Het formaat van oude source packages kan niet worden opgevraagd.\n"


regards,

Gerhard.

[GNUpdate-i18n] Update libpackman Dutch translation

[Bert De M. <BD...@Di...>]

Updated version !
Gerard,can you verify this maybe ?
cya,

Bert

Re: [GNUpdate-i18n] a little introduction ...

[Nerd T. <ner...@ho...>]

Hi there, seems we have an overflow of Dutch translators. My name is Rob 
Schilperoort, I live in a small city just east of Dallas, TX but was born 
and lived most of my life in the Netherlands.
I have been on vacation for the last few weeks without access to a computer 
(camping in Montana) so couldn't read my mail, should be getting more active 
from now on.

I have lot's of application design, modelling and coding experience but it 
is a little bit rusty.. I am planning to get some skills back up to date by 
doing translations here for a while.

Rob


>From: Bert De Meyer <BD...@Di...>
>Reply-To: gnu...@li...
>To: gnu...@li...
>Subject: [GNUpdate-i18n] a little introduction ...
>Date: 23 Jun 2002 11:20:55 +0200
>
>Just a little introduction ...
>
>My name is Bert De Meyer, I live in a small city called Leuven, known
>for it's university and the beer "Stella Artois", located some 30 km to
>the east of Brussels. During the day I work for a company called
>ABComputers in Brussels. We offer Solaris support on Sun hardware.
>Although I'm not a developer, I hope that I can contribute as a dutch
>translator to the project.
>
>cya,
>
>Bert
>
>
>
>
>
>-------------------------------------------------------
>Sponsored by:
>ThinkGeek at http://www.ThinkGeek.com/
>_______________________________________________
>GNUpdate-i18n mailing list
>GNU...@li...
>https://lists.sourceforge.net/lists/listinfo/gnupdate-i18n




_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

Re: [GNUpdate-i18n] New dutch Gpkg and Libcomprex translation

[Christian H. <ch...@gn...>]

On Thu, Jun 27, 2002 at 09:54:00AM +0200, Bert De Meyer wrote:
> I forgot to update some stuff in the headers (PO-Revision-Date
> Language-Team and Project-Id-Version ...), so here's the latest version.
> 
> Bert

Committed. Thanks!

Christian

-- 
Christian Hammond         <>  The GNUpdate Project
ch...@gn...      <>  http://www.gnupdate.org/
   I am not a vegetarian because I love animals; I am a vegetarian because I
   hate plants.
      -- A. Whitney Brown

[GNUpdate-i18n] New dutch Gpkg and Libcomprex translation

[Bert De M. <BD...@Di...>]

I forgot to update some stuff in the headers (PO-Revision-Date
Language-Team and Project-Id-Version ...), so here's the latest version.

Bert

Re: [GNUpdate-i18n] new Dutch libpackman .po

[Christian H. <ch...@gn...>]

On Wed, Jun 26, 2002 at 06:27:29PM +0200, Gerhard Muntingh wrote:
> Here it is!
> 
> 
> Gerhard.

Committed, thanks!

-- 
Christian Hammond         <>  The GNUpdate Project
ch...@gn...      <>  http://www.gnupdate.org/
   The Elder Gods went to Suggoth and all I got was this lousy T-shirt.

Re: [GNUpdate-i18n] Dutch translations

[Christian H. <ch...@gn...>]

On Wed, Jun 26, 2002 at 06:26:31PM +0200, Gerhard Muntingh wrote:
> On Wed, Jun 26, 2002 at 03:07:40PM +0200, Bert De Meyer wrote:
> Damn, I don't have that check_po.pl.  I do plan on using emacs
> once I've downloaded it :)

It's in each project's po/ directory, when you check it out from CVS.

Christian

-- 
Christian Hammond         <>  The GNUpdate Project
ch...@gn...      <>  http://www.gnupdate.org/
   The other line moves faster.
      -- Etorre's Observation

Re: [GNUpdate-i18n] Dutch translation

[Christian H. <ch...@gn...>]

On Mon, Jun 24, 2002 at 10:03:52PM +0200, Gerhard Muntingh wrote:
> > Something that also came to mind: Is there a limit to the length of a
> > string ? I see that some sentences are split in two, where others
> > aren't.
> 
> It should fit on an 80 character screen, but strings in a program
> are also used on other places that have other limits.

I try to never use fixed-size buffers unless I have to, and when I
do, they're usually around 4KB in length. I don't think you'll run
into any problems with long strings, but if you do, please let me know
and I'll get it fixed up.

As for output to a console, 80 characters is the limit, and around 75
is what I think things should be limited to when possible (so you
don't have, say, one character in that 80th column). Also keep in mind
that tab characters (\t) should always be considered 8 characters.

Christian

-- 
Christian Hammond         <>  The GNUpdate Project
ch...@gn...      <>  http://www.gnupdate.org/
   "Outside of a dog, a book is man's best friend. Inside of a dog, it's too
   dark to read"
      -- Groucho Marx

Re: [GNUpdate-i18n] Dutch translation

[Christian H. <ch...@gn...>]

On Mon, Jun 24, 2002 at 06:05:55PM +0200, Gerhard Muntingh wrote:
> 3. I notice `Warning' is sometimes `warning' and sometimes `WARNING'.
>    I don't know if it's done to indicate a degree of seriousness, but if
>    it's just a mistake, I'd happily translate them all to `Warning'.

Just inconsistency :) One of the things on my TODO list, which I want
to implement soon, is an alternative way of reporting errors. Instead
of fprintf, it'll be cxPrint() and pmPrint() and stuff, which will
take flags specifying warning, error, etc. That should make things a
bit more consistent, and Warning and stuff won't be in the strings
anymore.

I have a list of other things I'll be doing soon, probably before
that, so we'll see.

> 4. Can we use non-ascii characters?  Such as an `e' with dots on it.
>    I assume we can if we set the characterset in the Content-Type.

Yes.

> I think it should be very consistent across programs, so I was looking
> for some kind of translation standard.  I haven't been able to find
> one, but it might be a good idea to start a little doc with these
> kind of rules.

Not being any kind of expert in this, I don't know if there are any
standards. However, I am not opposed to having a doc for this on the
website.

Christian

-- 
Christian Hammond         <>  The GNUpdate Project
ch...@gn...      <>  http://www.gnupdate.org/
   He's got a magnet!! Everybody BACKUP!!!!

Re: [GNUpdate-i18n] Dutch translation

[Christian H. <ch...@gn...>]

On Mon, Jun 24, 2002 at 01:06:27AM +0200, Bert De Meyer wrote:
> Gerhard,
> 
> I don't know if we are only with 2 or more dutch translators.

Just two. I'll post a list of active translators hopefully in the next
few days (after I find out who is still with us).

Christian

-- 
Christian Hammond         <>  The GNUpdate Project
ch...@gn...      <>  http://www.gnupdate.org/
   Bugs come in through open windows.

[GNUpdate-i18n] Back from vacation

[Christian H. <ch...@gn...>]

Hi everyone.

Just want to let you all know that I'm back from vacation, and will be
answering any e-mails that came across the lists soon.

Christian

-- 
Christian Hammond         <>  The GNUpdate Project
ch...@gn...      <>  http://www.gnupdate.org/
   When all else fails, read the manual.

Re: [GNUpdate-i18n] Dutch translations

[Bert De M. <BD...@Di...>]

On Wed, 2002-06-26 at 18:26, Gerhard Muntingh wrote:
> On Wed, Jun 26, 2002 at 03:07:40PM +0200, Bert De Meyer wrote:
> > I suggest we take the ISO-8859-15 for future purposes. There isn't that
> > much difference anyway (euro signal ...)
> 
> Ehm, so we take the 15 now?  Or in the future.
> 
OK, I wasn't that clear :) 

I meant that it might be better to use the IS0-8859-15, because it is
the successor of the ISO-8859-1 and because the differences are rather
small (only some characters that aren't used that much any more and the
new euro symbol is inserted.) 

Bert 

[GNUpdate-i18n] new Dutch libpackman .po

[Gerhard M. <ger...@mu...>]

Here it is!


Gerhard.

Re: [GNUpdate-i18n] Dutch translations

[Gerhard M. <ger...@mu...>]

On Wed, Jun 26, 2002 at 03:07:40PM +0200, Bert De Meyer wrote:
> I suggest we take the ISO-8859-15 for future purposes. There isn't that
> much difference anyway (euro signal ...)

Ehm, so we take the 15 now?  Or in the future.


> (13 from the beginning of the string). Is that ok for you ?

Yes, fine.


> I checked the po files again with the check_po.pl command 
> and the libpackman file gave gave me 2 little errors:
> I don't know if you already changed this ...

Damn, I don't have that check_po.pl.  I do plan on using emacs
once I've downloaded it :)


> I also noticed that not every sentence is translated as "Kan niet"
> instead of "is mislukt" ?
> 
> can you verify that ?

Yes, I forgot one or two.  And the `failed to do' sentences
seem to be better with `mislukt'.


I'll post a new one,

Gerhard.

[GNUpdate-i18n] Dutch translations

[Bert De M. <BD...@Di...>]

You wrote:
>  - Charset should to be set.  I don't know what is should be.
>  	 Maybe `ISO-8859-15' or `ISO-8859-1'?

I suggest we take the ISO-8859-15 for future purposes. There isn't that
much difference anyway (euro signal ...)

>  - The alignment of {versie, branch, groep, licentie, grootte}.

How many spaces should I insert exactly ? I aligned the 
Naam,Versie,Release,Branch,URL,Group,Licentie,Arch,Grootte and
Samenvatting so that their ":" sign is at the same position. (13 from
the beginning of the string). Is that ok for you ?


I checked the po files again with the check_po.pl command 
and the libpackman file gave gave me 2 little errors:
I don't know if you already changed this ...


ENTRY: (nl.po, line 163)
  msgid "Unable to open package table at %ld\n"
  msgstr "Het openen van de package tabel op %ld is mislukt."
*** Missing trailing newline
ENTRY: (nl.po, line 175)
  msgid "Error: B+Tree: Unable to read the tree size.\n"
  msgstr "Fout: B+Tree: Kan de tree grootte niet lezen."
*** Missing trailing newline

I also noticed that not every sentence is translated as "Kan niet"
instead of "is mislukt" ?

can you verify that ?

cya,

Bert


On Mon, 2002-06-24 at 22:35, Gerhard Muntingh wrote:
> Hi,
> 
> Here is the new nl.po .  I changed a lot.  For example:
> all the `Het .... is mislukt' changed to `Kan niet ...'.
> 
> I used `package' after all, because it is a word the user
> has to know anyway.  Is that okay with you?
> 
> 
> regards,
> 
> Gerhard.
> ----

Re: [GNUpdate-i18n] Dutch gpkg translation

[Gerhard M. <ger...@mu...>]

On Tue, Jun 25, 2002 at 01:44:54PM +0200, Bert De Meyer wrote:
> I changed the files almost to all of your corrections except for the following:
> 
>  msgid "  -t, --test            - Doesn't actually perform file operations.\n"
> -msgstr "  -t, --test            - Doet eigenlijk geen echte bestandsuitvoering.\n"
> +msgstr "  -t, --test            - Doet geen echte bestands operaties.\n"
> 
> --> msgstr "  -t, --test            - Voert geen echte operaties op bestanden uit.\n"
> 
> ... seems more logical 

Even better!


> > -"      --upgrade,        - Upgrade de opgegeven package(s).\n"
> > +"      --upgrade,        - Vernieuw de opgegeven package(s).\n"
> > "        upgrade           Dit is hetzelfde als install.\n"
> 
> > `Vernieuw' or is `upgrade' common enough to use?
> 
> I think 'vernieuw' rather suggests that a package is being recreated instead of upgraded .
> but I do think that the sentence was a bit odd, so I changed it into this:
> 
> --> "      --upgrade,        - Upgraden van de opgegeven package(s).\n"

Yes, the user has to know the meaning of `upgrade' anyway.


> @@ -482,2 +482,2 @@
>  msgid "Could not create a temporary filename!\n"
> -msgstr "Het aanmaken van een tijdelijk bestandsnaam is mislukt!\n"
> +msgstr "Het aanmaken van een tijdelijk bestands is mislukt!\n"
> 
> --> msgstr "Kan een van een tijdelijk bestand niet aanmaken!\n"
> 
> As you did, I have changed all the 'is mislukt' sentences into 'Kan niet'

I've looked this text up in the sources, and it seems to be a mistake.
I'll post a patch to gnupdate-devel in a minute.

Looks almost finished to me.  Except for the following:

 - Charset should to be set.  I don't know what is should be.
 	 Maybe `ISO-8859-15' or `ISO-8859-1'?
 - The alignment of {versie, branch, groep, licentie, grootte}.
 - faze is written as fase.
 - You forgot quotes (") Around `Omschrijving' at line 193. 
 	 And another one at line 439.
 - You can fill in your name in the Last-Translator field if
   you like.

I think everything is ready for commit after this!

I found the gettext manual (info gettext) it has a section for
translators.


regards,

Gerhard.

[GNUpdate-i18n] Dutch gpkg translation

[Bert De M. <BD...@Di...>]

I changed the files almost to all of your corrections except for the following:

 msgid "  -t, --test            - Doesn't actually perform file operations.\n"
-msgstr "  -t, --test            - Doet eigenlijk geen echte bestandsuitvoering.\n"
+msgstr "  -t, --test            - Doet geen echte bestands operaties.\n"

--> msgstr "  -t, --test            - Voert geen echte operaties op bestanden uit.\n"

... seems more logical 

> msgstr ""
> -"      --upgrade,        - Upgrade de opgegeven package(s).\n"
> +"      --upgrade,        - Vernieuw de opgegeven package(s).\n"
> "        upgrade           Dit is hetzelfde als install.\n"

> `Vernieuw' or is `upgrade' common enough to use?

I think 'vernieuw' rather suggests that a package is being recreated instead of upgraded .
but I do think that the sentence was a bit odd, so I changed it into this:

--> "      --upgrade,        - Upgraden van de opgegeven package(s).\n"

@@ -482,2 +482,2 @@
 msgid "Could not create a temporary filename!\n"
-msgstr "Het aanmaken van een tijdelijk bestandsnaam is mislukt!\n"
+msgstr "Het aanmaken van een tijdelijk bestands is mislukt!\n"

--> msgstr "Kan een van een tijdelijk bestand niet aanmaken!\n"

As you did, I have changed all the 'is mislukt' sentences into 'Kan niet'

cya,

Bert

Re: [GNUpdate-i18n] new Dutch libpackman translation

[Bert De M. <BD...@Di...>]

On Mon, 2002-06-24 at 22:35, Gerhard Muntingh wrote:
> Hi,
> 
> Here is the new nl.po .  I changed a lot.  For example:
> all the `Het .... is mislukt' changed to `Kan niet ...'.
> 
> I used `package' after all, because it is a word the user
> has to know anyway.  Is that okay with you?
> 
> regards,
> 
> Gerhard.

Picobello ! :)

I'm going to make the same changes to the gpkg file.
I 'll send it afterwards...

cya,

Bert 

Re: [GNUpdate-i18n] Dutch translation

[Gerhard M. <ger...@mu...>]

> Something that also came to mind: Is there a limit to the length of a
> string ? I see that some sentences are split in two, where others
> aren't.

It should fit on an 80 character screen, but strings in a program
are also used on other places that have other limits.


regards,

Gerhard.

[GNUpdate-i18n] new Dutch libpackman translation

[Gerhard M. <ger...@mu...>]

Hi,

Here is the new nl.po .  I changed a lot.  For example:
all the `Het .... is mislukt' changed to `Kan niet ...'.

I used `package' after all, because it is a word the user
has to know anyway.  Is that okay with you?


regards,

Gerhard.

[GNUpdate-i18n] Dutch gpkg translation

[Gerhard M. <ger...@mu...>]

Hi,

I have some comments.  Some thing are also interesting for people who
don't know dutch. 

 - The {name, version, release, branch, .. } alignment problem.
 - The last two diffs.


@@ -27,3 +27,3 @@
 msgid "arg->var == NULL! Contact the developers.\n"
-msgstr "arg->var == NULL! Verwittig de developers.\n"
+msgstr "arg->var == NULL! Neem contact op met de developers.\n"

I don't know the word `Verwittig'.  Do you insist on using it?


@@ -38,3 +38,3 @@
 msgid "Warning: Argument `%c' is not a setting.\n"
-msgstr "Waarschuwing: Parameter `%c' is geen juiste waarde.\n"
+msgstr "Waarschuwing: Parameter `%c' is geen optie.\n"
 
@@ -43,3 +43,3 @@
 msgid "Warning: Argument `%s' is not a setting.\n"
-msgstr "Waarschuwing: Parameter `%s' is geen juiste waarde.\n"
+msgstr "Waarschuwing: Parameter `%s' is geen optie.\n"

This looks odd to me.  I'm not at all sure my solution is better,
but at least it doesn't look odd to me.


@@ -67,3 +67,3 @@
 msgid "Unable to find %s.\n"
-msgstr "%s niet gevonden.\n"
+msgstr "%s is niet gevonden.\n"

You did the same thing different on another line.  This makes it
consistent.


@@ -71,3 +71,3 @@
 msgid "Unable to retrieve a list of all packages.\n"
-msgstr "Het weergeven van een lijst van alle packages is mislukt.\n"
+msgstr "Het ophalen van een lijst van alle packages is mislukt.\n"

..


@@ -76,3 +76,3 @@
 msgid "You must specify at least one package name.\n"
-msgstr "U moet minsten één naam van een package opgeven.\n"
+msgstr "U moet minstens één naam van een package opgeven.\n"

..


@@ -139,3 +139,3 @@
 msgid "       Name: %s\n"
-msgstr "       Naam: %s\n"
+msgstr "        Naam: %s\n"
 
@@ -144,3 +144,3 @@
 msgid "    Version: %s\n"
-msgstr "    Versie: %s\n"
+msgstr "      Versie: %s\n"
 
@@ -149,3 +149,3 @@
 msgid "    Release: %s\n"
-msgstr "    Release: %s\n"
+msgstr "     Release: %s\n"
 
@@ -154,3 +154,3 @@
 msgid "     Branch: %s\n"
-msgstr "     Branch: %s\n"
+msgstr "         Tak: %s\n"
 
@@ -159,3 +159,3 @@
 msgid "        URL: %s\n"
-msgstr "        URL: %s\n"
+msgstr "         URL: %s\n"
 
@@ -164,3 +164,3 @@
 msgid "      Group: %s\n"
-msgstr "      Group: %s\n"
+msgstr "       Groep: %s\n"
 
@@ -174,3 +174,3 @@
 msgid "       Arch: %s\n"
-msgstr "       Arch: %s\n"
+msgstr "        Arch: %s\n"
 
@@ -179,3 +179,3 @@
 msgid "       Size: %d\n"
-msgstr "       Grootte: %d\n"
+msgstr "     Grootte: %d\n"
 
@@ -184,3 +184,3 @@
 msgid "    Summary: %s\n"
-msgstr "    Samenvatting: %s\n"
+msgstr "Samenvatting: %s\n"

You didn't translate everything (maybe you're right about that) and
I aligned it one space to the right.  I haven't tested gpkg with the
new .po file, but I think it should look right this way.


@@ -262,3 +262,3 @@
 msgid "  -t, --test            - Doesn't actually perform file operations.\n"
-msgstr "  -t, --test            - Doet eigenlijk geen echte bestandsuitvoering.\n"
+msgstr "  -t, --test            - Doet geen echte bestands operaties.\n"

I'm not at all sure about this.


@@ -297,3 +297,3 @@
 msgstr ""
-"      --upgrade,        - Upgrade de opgegeven package(s).\n"
+"      --upgrade,        - Vernieuw de opgegeven package(s).\n"
 "        upgrade           Dit is hetzelfde als install.\n"

`Vernieuw' or is `upgrade' common enough to use?


@@ -400,3 +400,3 @@
 "      --diff,           - Geeft als output een diff weer van twee packages\n"
-"        diff              of van een package tegenover de database.\n"
+"        diff              of van een package tegen de database.\n"
 
?I'm not sure here?


@@ -436,5 +436,5 @@
 msgstr ""
-"WARNING: gpkg is nog in een development faze, en is gevaarlijk\n"
+"WARNING: gpkg is nog in een development fase, en is gevaarlijk\n"
 "         voor normaal gebruik. Indien je geen developer bent,\n"
-          gebruik dit dan alstublieft enkel voor het nagaan van packages.\n"
+"          gebruik dit dan enkel voor het opvragen van packages.\n"

First informal, and then formal?  I removed the `alstublieft'.
Query is completely different from nagaan, I think `opvragen' is better.


@@ -450,3 +450,3 @@
 msgid "A command must be specified!\n"
-msgstr "Een commando moet opgegeven worden!\n"
+msgstr "Er moet een commando opgegeven worden!\n"

Short sentences vs. full sentences?  What's better?


@@ -482,2 +482,2 @@
 msgid "Could not create a temporary filename!\n"
-msgstr "Het aanmaken van een tijdelijk bestandsnaam is mislukt!\n"
+msgstr "Het aanmaken van een tijdelijk bestands is mislukt!\n"

I think this is a bug in the code, don't change the translation if
you're not sure.  Shouldn't it be `temporary file'?


regards,

Gerhard.

Re: [GNUpdate-i18n] Dutch translation

[Bert De M. <BD...@Di...>]

> 1. Be formal or informal (`U' vs. `je').
 
I tend to mostly formal with translations... I see that the French
translation is also more formal (e.g. Vous instead of Tu)

> 2. To start sentences with words like `de'-`het'-`een'
>    (English: `the', `a', `an').

Depends mostly on the contents of the sentence ... it should be easy to
understand for any user, but we need to stay close to the original text
as possible.

> 3.I notice `Warning' is sometimes `warning' and sometimes `WARNING'.
>   I don't know if it's done to indicate a degree of seriousness, but
>   if it's just a mistake, I'd happily translate them all to `Warning'.

I agree with you, I had the same question ...

> 4. Can we use non-ascii characters?  Such as an `e' with dots on it.
>    I assume we can if we set the characterset in the Content-Type.
 	 
I didn't pay any notice, this is indeed a good question. It's best to
set a characterset indeed.

> 5. I use sometimes the wordt `ongeldig' where you use `onjuist'.

'Ongeldig' is indeed a better suited word.

> 7. I translated `package' to `pakket' where you didn't.
	 
I didn't know for some specific words if it was best to let them 
be or to translate, but 'pakket' seems ok for me.


Something that also came to mind: Is there a limit to the length of a
string ? I see that some sentences are split in two, where others
aren't.


Bert