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

• 

  • Reply
  • #5

  Phanx Sat, 15 Aug 2009 01:00:48

  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.

• 

  • Reply
  • #4

  Drool Wed, 21 Jan 2009 23:26:14

  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

• 

  • Reply
  • #3

  ckknight Fri, 16 Jan 2009 21:38:16

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

• 

  • Reply
  • #2

  Phanx Fri, 16 Jan 2009 03:47:23

  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.

• 

  • Reply
  • #1

  ckknight Thu, 15 Jan 2009 16:00:02

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