#2257: .po files : same msgid records could be "deduplicated"
-------------------------+--------------------------------------------------
 Reporter:  rejoc        |        Owner:  rejoc   
     Type:  enhancement  |       Status:  new     
 Priority:  normal       |    Milestone:  1.1b4   
Component:  I18n         |      Version:  1.1 HEAD
 Severity:  normal       |   Resolution:          
 Keywords:  i18n         |  
-------------------------+--------------------------------------------------
Comment (by Gustavo):

 Replying to [comment:5 rejoc]:
 > Replying to [comment:3 Gustavo]:
 > > rejoc:
 > >
 > > All what you're describing is the intended behavior of Gettext. That's
 how things work on every single Gettext-powered application (this is,
 nearly all the applications you're using). And there's no bug in that
 behavior.
 > >
 > >
 > We are not using the plain Gettext tools but their specific
 implementation in TG.

 Gettext is not only a set of tools, it also defines an standard. So every
 implementation should comply with the standard.

 (It's good to be aware that TG1 had its own implementation; I didn't know
 that)

 > Gettext documentation specifies that having duplicated msgid in a .po
 file ''"is invalid input for other programs like msgfmt, msgmerge or
 msgcat" (9.5 Invoking the msguniq Program)''.

 Exactly. Did you see how I handled that in the script I attached? That's
 not a bug, it's the intended behavior.

 > tg-admin i18n collect generates such duplicates. Is it the correct
 behavior as the .pot generated it supposed to be the input to "tg-admin
 i18n merge" (emulating msgmerge) and "tg-admin i18n compile" (msgfmt) ?

 I don't know how TG1 handles that, since you say it has its own
 implementation. What I do know is that xgettext (or equivalent) must *not*
 do anything with duplicate messages. Duplicate messages ''must'' be
 handled with msguniq and/or msgcomm, or equivalents.

 Again, there's no such bugs. It's all part of the intended and documented
 behavior.

-- 
Ticket URL: <http://trac.turbogears.org/ticket/2257#comment:6>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to