ITT: Context hints?

[Borut]

There are now clones of English original strings, in order to accommodate for translations that are dependent on the context in which these strings appear - for inflected languages. This is nice and needed. An example would be the string "all selected items", which appears three times.

Question: Is there any possibility for a translator to have some hint in the ITT about the usage of such strings?

[SkyFrontier]

Variation:
translators could be able to state comments in the format:

translation {>{notes}<} (or something easier and unique)

which optionally could pop as tooltips or just sit there. Current comments model wasn't of any use, to me - and I badly missed a (modularly searchable!!!, ie, could be searched independent of main original/translation core) better, export-able per-string note taking ability (see my numerous notes shared here
http://www.xyplorer.com/xyfc/viewtopic.php?f=12&t=8855
and here
http://www.xyplorer.com/xyfc/viewtopic.php?f=12&t=8758).

[admin]

There are now clones of English original strings, in order to accommodate for translations that are dependent on the context in which these strings appear - for inflected languages. This is nice and needed. An example would be the string "all selected items", which appears three times.

Question: Is there any possibility for a translator to have some hint in the ITT about the usage of such strings?

Sorry, I did not get it.

[Borut]

Shall try to reformulate...

How can a translator correctly translate various occurrences of the same string into an inflected target language, without knowing the context in which each of these string instances is being used (i.e. without knowing the other string with which it is being used in GUI)?

It is really an extremely tedious trial and error job - after solving just one such occurrence I was quite near quitting the translation effort altogether.

Here what I was doing:

• A: In ITT, tag each string clone with a unique ID, for instance *1*, *2*,...
  B: Save .lng and exit ITT
  C: Try to find the occurrences of these strings in GUI, i.e. places in which the IDs can be seen now;
  D: Note which ID appears in which context;
  E: Go back to ITT, inflect the translated strings according to notes taken in the previous step and remove the IDs
  F: Save .lng and exit ITT
  G: Back in GUI, make QA
  H: If not OK, go again to A (more or less) and repeat

Hope that now my description is more understandable.

[admin]

You have a concrete example?

[Borut]

Yes - it is the string "all selected items" (have mentioned it in the first message of this thread). If you put that in the ITT filter and scroll to the end of a list, you will see the three of them. In GUI they are used in Favorites > Add tags AND Edit tags. The third usage place not known ATM.

BTW, I am aware that this could be an impossible problem for you to solve in ITT (or a very tough one). It is however the fact that translators in these cases have a very tough and time consuming task (at least that is my experience).

[admin]

Yes - it is the string "all selected items" (have mentioned it in the first message of this thread). If you put that in the ITT filter and scroll to the end of a list, you will see the three of them. In GUI they are used in Favorites > Add tags AND Edit tags. The third usage place not known ATM.

BTW, I am aware that this could be an impossible problem for you to solve in ITT (or a very tough one). It is however the fact that translators in these cases have a very tough and time consuming task (at least that is my experience).

Oh yes, this is rather an ITT bug. The clarifying information has always been in the LNG file:

Code: Select all

ms.2129=00|all selected items{attached to}|--|all selected items
ms.2130=00|all selected items{removed from}|--|all selected items
ms.2131=00|all selected items{the tags of}|--|all selected items

... but the ITT did not display it. Fix comes.

[Borut]

... but the ITT did not display it. Fix comes.

Works great in 11.90.0010. Very cool. Thank you!