On Tue, Mar 12, 2013 at 11:30:38AM +0900, Daiki Ueno wrote: > Raphaël writes: > >> /tmp/a.po: warning: Charset missing in header. > >> Message conversion to user's charset will not work. > >> /tmp/a.po:13: duplicate message definition... > >> /tmp/a.po:2: ...this is the location of the first definition > >> msguniq: found 1 fatal error > > > > IHMO this is a bug. > > Although the error message is not too intuitive, I suppose it is an > intended behavior that msguniq treats the empty msgid specially. [...] > (As you know, the empty msgid is kind of reserved for PO file headers.)
ok, thank you for the information. Is there a reference somewhere where is written that "applications must not generate entries for the empty string"; so that I have a chance the po-generator get fixed in the future ? best regards
