Bug #78457 Use gettext and .po(t) files for translations
Submitted: 16 Sep 2015 14:17
Reporter: Daniël van Eeden (OCA) Email Updates:
Status: Open Impact on me:
None 
Category:MySQL Server: Errors Severity:S4 (Feature request)
Version:8.0 OS:Any
Assigned to: CPU Architecture:Any
Tags: errors, i18n, internationalization, messages

[16 Sep 2015 14:17] Daniël van Eeden 
Description:
Please use gettext for translating strings in the server and client if possible.

This would:
- Not only translate errors (not all translated errors are really errors now...)
- Allow the different translation communities to start translating MySQL.
- Allow the use of tools like transifex, launchpad, poedit
- Automatically mark translated strings as fuzzy when the original changes.

https://www.transifex.com/
https://translations.launchpad.net/
https://poedit.net/

How to repeat:
See description
[25 Sep 2015 4:48] Laurynas Biveinis 
Semi-relatedly, if server error log messages are to be translated at some point in future, I wish InnoDB team did not migrate from printf("foo bar %s baz %d") diagnostics to log << "foo bar " << str << "baz " << num, but used e.g. Boost::Format: log << format("foo bar %1% baz %2%") % str % num
[18 Jun 2016 21:27] Omer Barnir 
Posted by developer:
 
Reported version value updated to reflect release name change from 5.8 to 8.0