On 22 February 2013 13:57, TJ Frazier <tjfraz...@cfl.rr.com> wrote: > Hi, Jan, > > > On 2/22/2013 06:21, janI wrote: > >> On 22 February 2013 10:10, Jürgen Schmidt <jogischm...@gmail.com> wrote: >> >> On 2/22/13 9:45 AM, janI wrote: >>> >>>> On 22 February 2013 09:30, Andre Fischer <awf....@gmail.com> wrote: >>>> >>>> On 22.02.2013 08:29, janI wrote: >>>>> >>>>> Hi. >>>>>> >>>>>> the .src sources relatively often contain a text line: >>>>>> >>>>>> text [x-comment] = "..." >>>>>> >>>>>> most times the ... is empty, but it also contains english text, and in >>>>>> >>>>> one >>> >>>> case a multibyte charecter text. >>>>>> >>>>>> >>>>> Hi Jan, >>>>> >>>>> I do not know the answer but would like to make a guess: >>>>> the x-comment "language" is used to annotate the actual string with a >>>>> message from developer to translator. >>>>> >>>>> My guess is based on some very hazy memory and by looking at files like >>>>> officecfg/registry/data/org/****openoffice/Office/Embedding.****xcu >>>>> >>>>> Lines 27 to 31 for example look like this: >>>>> >>>>> <node oor:*name=*"Verbs"> >>>>> <node oor:*name=*"PRIMARY" oor:*op=*"replace"> >>>>> <prop oor:*name=*"VerbUIName"> >>>>> <value>Primary</value> >>>>> <value xml:*lang=*"x-comment">Is not shown in UI. No >>>>> >>>> translation >>> >>>> is required.</value> >>>>> </prop> >>>>> >>>>> >>>>> If I am right then today you would write this like this: >>>>> >>>>> <node oor:*name=*"Verbs"> >>>>> <node oor:*name=*"PRIMARY" oor:*op=*"replace"> >>>>> <prop oor:*name=*"VerbUIName" oor:localized="false"> >>>>> <value>Primary</value> >>>>> </prop> >>>>> >>>>> Note the additional >>>>> oor:localized="false" >>>>> in the <prop> tag. >>>>> >>>>> the trigger today is the missing "xml:*lang=" only tags with that are >>>> extracted. >>>> >>>> the x-comment are not extracted to the sdf files, so the translators >>>> >>> never >>> >>>> gets the information. >>>> >>>> >>>> But again, this is only a guess, not a fact. >>>>> >>>>> Thx for your guess, it works well with my guess (meaning I could >>>> remove >>>> x-comment). >>>> >>>> I hope someone has some cool facts. >>>> >>> >>> no cool facts but Andre's guess sounds reasonable and it is possible >>> that it was an idea to provide some context information to translators >>> but that the process was never finalized. >>> >>> Juergen >>> >>> >> Both you and andre are in sync with what I think. >> >> If nobody objects within the next 72 hours using lazy consensus, I will >> remove x-comment, and the new tool (just as the current tool) will not use >> the messages. >> >> rgds >> Jan I. >> >> Just a suggestion (not an objection; I'm not the one doing any of the > work!). > > (1) IMHO, any human-readable language that does not have some "comment" > facility is seriously deficient. I am thinking of everything from a simple > asterisk in column 1, to the elaborate HTML "<!-- ... -->" which we > sometimes see on the wiki. > (2) Assuming that your output language(s) have such a facility, you might > consider transforming "x-comment" into a comment in the output. > > /tj/
I understand and share your concern, but the current x-comments would in my opinion not serve a usefull purpose, and with the .po file demand I have no way of adding comments. had we as a community gone for the xml solution, we would have a comment field among other nice features. so to cut it short, I would like to provide the most information posssible to translators but comments is not supported by the .po file structure. rgds jan I. > > > >>> >>>> rgds >>>> Jan I. >>>> >>>> >>>>> -Andre >>>>> >>>>> >>>>> >>>>> We have no language "x-comment", and it is currently not extracted, >>>>>> however >>>>>> there are a couple of places in the code noting it is automatically >>>>>> loaded. >>>>>> >>>>>> So my questions are: >>>>>> 1) Is this leftovers from and older version, and no longer used ? >>>>>> 2) if not, how is it used ? >>>>>> 3) if not, should it be translated (if it can appear in the ui it >>>>>> >>>>> should >>> >>>> be >>>>>> translated) ? >>>>>> >>>>>> thanks in advance for your help >>>>>> Jan I. >>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >>> >> > >
