lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Once upon a time Visual Basic for Applications in Microsoft Office applications were localized. So, a macro for your spanish Excel had to be written in spanish, as in your examples ("si... entonces..."). Aaaaaaand error messages were so horribly worded and other-guy-in-internet-with-the-same-problem impaired as to be useless.

It was Hell.


On 10/29/2014 12:11 PM, Javier Guerra Giraldez wrote:
On Wed, Oct 29, 2014 at 12:51 AM, - <> wrote:
Please move all message strings to one header file.
It greatly simplifies the localization of a Lua engine.

I think this is a bad idea in itself.  any message generated by the
engine itself should be considered part of the implementation, not to
be shown to a user.

most people would agree that it would be foolish to translate the
language keywords (i wouldn't like to write "si calza(cadena, patrón)
entonces imprimir ('de acuerdo') fin" instead of "if match(string,
pattern) then print ('OK') end" ).  What about the names of the value
types? ("number", "table", etc), or the library function names?  as
noted by Roberto and Michal, some messages use those names as part of
the text.

As long as the language (and libraries) allow you to write your
programs that interact with the user in any language you care about,
then there's no need for further "localization" of the engine.