1020 - Allow localization phrases to be grouped (optionally)

I have different "sections" of localizations in my files and the output of the app bundles them all together.

I'd like to be able to group phrases so that I can have those phrases print out by group.


Group 1

Phrase 1
Phrase 2
Phrase 3

Group 2

Phrase 4
Phrase 5
Phrase 6

This will make the localization files much more readable.

Optionally allow the group to have a description field which would put a comment in the output:

-- General strings
L["Filters"]                = true
L["All"]                    = true
L["None"]                    = true
L["Ok"]                        = true

-- Command line options
L["Profile"]                = true
L["Filter"]                    = true

User When Change
Torhal Jul 24, 2013 at 21:37 UTC
Ackis Jan 26, 2011 at 21:58 UTC Changed assigned to from ckknight to prencher
Ackis Mar 24, 2009 at 18:54 UTC Changed component from None to Component #196
Ackis Feb 11, 2009 at 16:30 UTC Changed component from None to Component #196

Changed status from Accepted to New
Ackis Jan 05, 2009 at 22:28 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Phanx Phanx Aug 15, 2009 at 01:00 UTC - 0 likes

    A bit late, but I'd just like to reply to ckk's comment about "that's what phrase context is for".

    For example, let's say I have an option labeled "Counter Size", and that when moused over in game, this option's tooltip explains that this option exists to "Set the text size of the shield charge counters". Furthermore, this option is grouped together with several other options that adjust the sizes of different text elements of my addon.

    When I compile a locale file by hand, I can logically group these two translations together, and group them with the translations of related options, and group them under the translation for this option group's header. A translator reading this locale file does not need to load the addon in-game to learn the context, as it is obvious by the intentional ordering of translations which mirror the ordering of options in-game. He can also see that related phrases are very similar, and save time by using the same phrase recycling as is used in the English translations.

    Your suggestion means that I should write additional text for every single translation. So, next to "Counter Size" I should write "Label for option to adjust the text size of shield charge counters", and next to "Set the text size of the shield charge counters" I should write "Tooltip description for option labeled 'Counter Size'". This is more work for me to write all this extra stuff, and more work for translators to read all this extra stuff and piece it together when it's scattered all over the place, and is totally unnecessary in an intelligently organized list of phrases.

    For some projects, like BabbleZone, it makes sense to simply put everything in alphabetical order; there is a huge number of phrases to translate, and they are all contextually identical (the names of places in the game), so alphabetizing does not hinder understanding by translators and actually improves maintainability by making specific translations easy to locate.

    For other projects, though, it just doesn't make sense, and it would be really nice if there were some way to manually order phrases. Even something as simple as preserving the order of phrases when pasting into the import form would solve the problem.

  • Avatar of Drool Drool Jan 21, 2009 at 23:26 UTC - 0 likes

    Could I suggest, in addition to grouping, a phrase's context be put as a comment at the end of the line:

    L["N/A"] = true -- abbreviation for Not Available

  • Avatar of ckknight ckknight Jan 16, 2009 at 21:38 UTC - 0 likes

    Phanx, for your second issue, that's what phrase context is for.

  • Avatar of Phanx Phanx Jan 16, 2009 at 03:47 UTC - 0 likes

    Agreed. In my actual files, I group together option names, descriptions, and selection labels, but the CurseForge translation system just alphabetizes everything indiscriminately. Not only does this make things less readable, it also means that translations will probably have to install the addon to figure out what strings are supposed to mean, instead of being able to see "Option Name", "Brief description of option", "Choice A", "Choice B", etc. Some kind of grouping or manual ordering is a must.

  • Avatar of ckknight ckknight Jan 15, 2009 at 16:00 UTC - 0 likes

    There's namespacing stuff in now, though it serves a different purpose than this.



Last updated
Jul 24, 2013
Jan 05, 2009
Declined - We decided not to take action on this ticket.
Enhancement - A change which is intended to better the project in some way
Medium - Normal priority.

Reported by

Possible assignees