Laboratoire ICAR » Plateforme TXM

Define and implement String messages workflow and update guidelines.

Discuss about this massive ticket.

Some scripts of org.txm.translate automate some tasks:
- Finds duplicated messages in all core and rcp plug-ins.
- Merges them in a new key and move them to org.txm.core or org.txm.rcp.
- Finds unbounded messages and saves them to a file.
- Checks that all key defined in Messages.java class are used in the source files AND removed the unused keys
- need to check and validate other scripts

Write the workflow of scripts apply and manual task to do for each target.
Also check the guidelines to adapt them to the scripts.

TODO: check the steps above are in the guidelines

• use the specifications of https://groupes.renater.fr/wiki/txm-info/public/nommage_symboles_externalisation for keys naming
• move common strings that can be shared to classes TXMCoreMessages and TXMUIMessages
• do not externalize/translate log string of level "finest" (add //$NON-NLS-1$)
• do not externalize/translate log string of level "severe" (add //$NON-NLS-1$)
• use NLS binding system (with {0}, {1}, etc. and stop to concatenate strings. The concatenation will lead to problems in some languages)
• TBD

TODO: create a new issue to apply workflow to existing source code