Opened 14 years ago

Closed 10 years ago

Last modified 2 years ago

#84 closed enhancement (wontfix)

Making translators' lives easier (almost copy & paste from my post at

Reported by: guest Owned by: Eugene Romanenko
Priority: minor Milestone: 1.4.0
Component: Lucide Core Version: 1.0 Beta 3
Keywords: easier translation Cc:


[ eComStation Developer Group ] I've just had a look at the source .lng file for Lucide translation.

It's short, it's plain text, it seems to be structured... but is NOT. It's easy to produce a translation for Lucide, but not so easy to produce a good one (perhaps some defects are inherited from NewView? here?). What's wrong?

BTW, this is not intended to be a pun against Eugene Romanenko, but a constructive criticism that may be used by developers pf NLV-enabled apps to make translators' lives easier.

-Resource strings are split into groups starting with 'MENU_', 'TBHINT_' and the like. This is good, but strings within groups are hardly sorted, so you can't relate them to each other adequately (as you would if they resembled menu nesting, group boxes, etc. item order).

For example, to choose adequate mnemonics for user menus it is most convenient to have them in nested lists, ordered so that items in the list match the order in which they appear on the user menu. This happens most of the time, except that menu subgroups are shuffled around, or perhaps you are translating 'document' menu items and you suddenly find a subgroup from 'view'...

-Strings from each group can be related to strings in other groups. An obvious example is items-toolbar hint pairs. While it is very sensible to group menu items, it makes a little less sense to group hints, except perhaps for length comparison.

Parhaps a good solution would be a 2-column table for each app element (such as the user menu or dialog boxes) ordered by item (first column), with item-hint couples in each row. Of course, I mean user-editable columns; obviously there should be column for IDs, etc...

Just $0.02 more.

Regards, Alfredo.

Change History (5)

comment:1 Changed 14 years ago by guest

Type: defectenhancement

comment:2 Changed 11 years ago by Silvan Scherrer

Milestone: 2.0 and further

comment:3 Changed 10 years ago by Silvan Scherrer

Resolution: wontfix
Status: newclosed

comment:4 Changed 5 years ago by Lewis Rosenthal

Milestone: 2.0 and furtherFuture

Milestone renamed

comment:5 Changed 2 years ago by Gregg Young

Milestone: Future1.4.0

Move closed tickets to completed milestone. Many of these were completed before 1.4.0

Note: See TracTickets for help on using tickets.