Some translated strings don't get saved

Asked by Emilien Klein

Apparently some strings I translated in the JOSM trunk template in French [1] didn't get saved. Here are the strings that show up as untranslated, even though I translated them and clicked on "Save & Continue" (the "new translation" radio button was selected).

It happens with those 4 strings (until now, maybe more to come):

- 636: Object of type {0} with id {1} was marked to be deleted, but it's missing in the source dataset
** L'objet de type {0} ayant pour id {1} a été marqué pour être supprimé, mais il n'est pas présent dans le jeu de données source

- 1827: Warning: failed to parse Mappaint styles from ''{0}''. Error was: [{1}:{2}] {3}
** Avertissement : échec de l'analyse des styles Mappaint depuis "{0}". L'erreur est : [{1}:{2}] {3}

- 1828: Warning: failed to parse Mappaint styles from ''{0}''. Error was: {1}
** Avertissement : échec de l'analyse des styles Mappaint depuis "{0}". L'erreur est : {1}

- 2596: Error fetching URL {0}
** Erreur lors de la récupération de l'URL {0}

- 2943: Delete tool "{0}"?
** Supprimer l'outil "{0}" ?

I've supplied the French translation so that someone can try submitting those translations to see if they get saved.

The strange part is that those where on the same page as other strings I translated that all got saved... It doens't seem to be a temporary database failure, since I can constantly reproduce it while other strings on the same page successfully get translated/saved.

I noticed this when I got shown the same string to translate again, and when I double clicked in the empty textbox to translate, Firefox showed me the text I had already translated. That seemed weird, and then I noticed more strings I had just translated but that were still presented as untranslated...

[1] https://translations.launchpad.net/josm/trunk/+pots/josm/fr/+translate?show=untranslated

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Данило Шеган (danilo) said :
#1

Hi Emilien, I believe this is a bug that was already reported: actually a combination of two bugs (one where LP doesn't show that it hit an error when verifying a string, and another where verification is broken for Java-format strings). I even think the latter is a bug in upstream gettext library (library that Launchpad is based on, and which is used for error checking).

Related bugs are bug 438751 and bug 495207. One of them is marked 'incomplete' because we need someone to check if JOSM PO files pass all the msgfmt checks.

Can you help with this problem?

Provide an answer of your own, or ask Emilien Klein for more information if necessary.

To post a message you must log in.