2012/1/28, Martin-Éric Racine <[email protected]>: > Sorry, but it seemed that my original packaging was wrong to begin > with. According to the manual page of dictionary-common-dev, the > content of that field *should* be "name in that language (name in > English). That's why I changed it. I welcome ideas on how to handle > upgrades, but changing it back to what was an incorrect order doesn't > sound like a good idea.
Hi, Martin and Andreas With the proposed changes (use of elanguage for displaying the correct string and language string preserved) things will be displayed properly, just the internal identifier will stay the same old one, but it is mostly of internal use. For the only case I know where it is used (squirrelmail) the ordering is of little importance. The annoyance caused in unattended upgrades by changing internal identifier is far worse than the effect in this corner case, so I think changing things as proposed is a good idea and the way to go. One of the reasons for elanguages implementation was to smoothly correct display of wrong language entries without disturbing upgrades, just as is needed here. PS: Andreas, thanks for the retitle, I had to send the message from gmail and had no control over line lenght. Regards, -- Agustin -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
