- Ticket details
51 - Translation System for AddOns
This idea came up on WoWAce before, but since the wowace rewrite was scratched for CF, forwarding the request:
I would like a simple, but yet effective, system to allow Authors to put up strings that need localization, and for translators the possibility to submit those translations to the author.
Automatic generation of some kind of Lua Format, or CSV Format, or whatever, so a script could parse it and generate locale files in the addons required Format would be win-win.
I could think of a layout like this:
<original string> ( .. <description> .. ) -- <input for translated string>
description being optional to describe the context of some strings, might be useful for very short words, that require a certain context to be understandable ;)
- Comments
- Facts
| Last updated on: | 10/13/2008 09:35:06 |
|---|---|
| Reported on: | 05/12/2008 21:19:24 |
| Status: | Started |
| Type: | Enhancement |
| Priority: | High |
- Reported By
|
|
|---|
- Possible Assignees
|
|
|---|
- Votes
Just an Idea, but it would be nice to have a "Download localized addon", where you select (check boxes) the localized versions you want included in your locale.lua (just append them after one another) when you download your addon. Most people only use 1 locale, tops 3?
Could save you some bandwidth (a little here, a little there), and the end user have a tiny bit less code to be compiled/run.
Vote!!!
One global localization file will be easier to manage.
Especially checking for some later additional lines between version upgrade.
BTW, The author of Alar series addon have his personal webpage with an localize page for translator to help with translation.
NEED
THIS
NOW!!! :D :D
I know the export is working fine, what is the progress on an import functionality?
Also, since it auto-generates items, is it possible to have it generate (optionally) the following:
Header - Something you plug in that you want Credits - A list of all people (sorted by date of contribution, or by number of contributions) that have contributed to the translations for that local Translations - The output that currently exists
So for example:
Add on foo localization in enUS:
--[[
foo-enUS.lua
Localization strings for enUS
Credit to:
Joe, Bob, Smith, XXX, ...
]]--
Local stuff here
Another possibility is to allow a keyword substitution in the template?
I don't think I'd ever call a translator lazy. Its by no means an easy task, even if you speak both languages fluently.
Translators now become more lazy...and more stupid...
Anyway, vote for it.
Because this sort of thing will happen eventualy and there will be bitching.
-in the file / page that has the completed localizations (if not done by many) allow the translator a one line credit? or put in that it was translated by the people at curseforge-translation project.
Voted, we need this.
I'd suggest YAML as format for the localisation files.
Maybe the files could get automaticly generated (parsed) from the addon files, like gettext does
The simplest route would be to have the dev paste a basic lua table. Values are taken to be localized, and comments are also displayed to the localizer. For example:
{
["Some key"] = "This is an English string",
ANOTHER_KEY = "Blah (.*)", -- Needed to parse the chat log
}
Of course, in converse, the output would also be a simple lua table in the same format for the dev to copy/paste into their locale file. You should probably give an option to include the english string for strings not yet localized as well, some devs will use a library or metatable that will do that automatically for them, some will not.
Oh and lastly, it'd probably be best to escape out special chars, to avoid issues caused by crappy text editors (I'm looking at you koKReans).