On 24 August 2013 12:01, Dick Groskamp <[email protected]> wrote:
> Op 24-8-2013 8:36, janI schreef: > >> On 24 August 2013 00:54, Regina Henschel <[email protected]> wrote: >> >> Hi Jan, >>> >>> janI schrieb: >>> >>> On 23 August 2013 20:25, Mr. Phan Anh <[email protected]> wrote: >>>> >>>> Here is the string that you said: >>>> >>>>> ___________________________ >>>>> <link href="text/shared/01/02180000.****xhp" >>>>> name="Verknüpfungen...">****Verknüpfungen...</link> >>>>> >>>>> ___________________________ >>>>> The problem you have said would be the confusion between the ability to >>>>> translate or untranslate phrase "name="Verknüpfungen..." in between >>>>> <link......> >>>>> >>>>> Let me clarify them by X: the translation that has to be translated >>>>> and Y: the translation that you are confusing in translating or not. >>>>> >>>>> <link........name=YYY> XXX <link> >>>>> >>>>> >>>>> You wondered that would be it possible to translate the phrase "YYYY" >>>>> The solution based on Vietnamese Translation are: >>>>> a. You can translate it. >>>>> b. Some translators just translated the "main content" which is XXX. >>>>> They translated the XXX into their native language. >>>>> But some translators didnt translate YYY >>>>> The choice is based on you. >>>>> >>>>> Wrong !! >>>>> >>>> text inside <...> are not to be touched only the text Y in <x>Y</x> may >>>> be >>>> translated. >>>> e.g. the name= is a directive to the help system, if you translate that, >>>> help will not work. >>>> >>>> I'm not sure about that. The specification [1] says in the reference, >>> "This is the link name, needed to >>> fulfill accessibility requirements." >>> >>> And these are the examples given, >>> "Please refer to <link href="http://www.openoffice.****org< >>> http://www.openoffice.org>**" >>> >>> name="Link to >>> the OpenOffice.org Website">the <emph>OpenOffice.org</emph> >>> website</link> for further details." >>> "More details can be found in <link >>> href="text/common/guide/****overview.xhp" name="Link to the >>> overview">the >>> overview</link>." >>> >>> You picked the one example where it actually does not matter what you >> do, >> because that tag is not interrelated >> >> Look at >> <variable id=\"control_properties\"><**link >> "href=\"text/sbasic/guide/**control_properties.xhp\" name=\"Changing the >> "Properties of Controls in the Dialog Editor\">Changing the Properties of >> Controls in the Dialog Editor</link></variable>" >> >> If you start translating id=, the whole indexing will not work. There are >> many similar examples where name= is used for indexing. Of course if you >> really know what you do, and make 100% that you translate the tree files >> identical, then it will work. >> >> Since it is difficult enough to understand what to translate and what not, >> simple rules work far better (and leave the few exception). Therefore a >> recommendation >> - never translate inside <...> >> is easy to follow. >> >> rgds >> jan I. >> >> >> Both sound, as if the value of the name attribute should be spoken by an >>> accessibility application. If this is indeed the purpose, then it should >>> be >>> translated. >>> >>> [1] >>> Understanding, Authoring and Editing >>> OPENOFFICE.ORG HELP >>> http://www.openoffice.org/****documentation/online_help/**<http://www.openoffice.org/**documentation/online_help/**> >>> OOo2HelpAuthoring.pdf<http://**www.openoffice.org/** >>> documentation/online_help/**OOo2HelpAuthoring.pdf<http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf> >>> > >>> >>> Kind regards >>> Regina >>> >>> >>> >>> >>> ------------------------------****----------------------------** >>> --**--------- >>> To unsubscribe, e-mail: >>> l10n-unsubscribe@openoffice.****apache.org<http://apache.org> >>> <l10n-unsubscribe@**openoffice.apache.org<[email protected]> >>> > >>> For additional commands, e-mail: [email protected].****org< >>> l10n-help@openoffice.**apache.org <[email protected]>> >>> >>> >>> Jan, > > as far as I know Regina is right. > In my Dutch translation ALL the tags "name= " are translated into Dutch. > They make up the index for the Help and so they SHOULD be translated. > > Bare in mind: ONLY the part AFTER "name=" is to be translated, so you are > ending up with things like > > "To continue the search, click the <link > href=\"text/swriter/01/**02110100.xhp\" > " > "name=\"Repeat Search\"><emph>Repeat Search</emph></link> icon on the " > "<emph>Navigation</emph> toolbar." > > what will be > > "Klik op het pictogram <link href=\"text/swriter/01/**02110100.xhp\" > name=\"Zoeken " > "herhalen\"><emph>Zoeken herhalen</emph></link> op de werkbalk " > "<emph>Navigatie</emph> om de zoekopdracht voort te zetten." > > in Dutch > > and > > "<link href=\"text/swriter/01/**02120000.xhp\" > name=\"AutoText\">AutoText</**link>" > "<link href=\"text/swriter/01/**02120000.xhp\" > name=\"AutoTekst\">AutoTekst</**link>" > > As far as I know the part after "name=" is the only part inside <link ... > /link> to be translated > > Can be remembered by: after "name=" always a double translation follows > > But you are right about "id=" That is NOT to be translated, only the part > after "name=" between <link ... /link>" > > This way you will have a translated index for the index > I am just the programmer that rewrites the engine behind all this, but if you want to recommend the extra burden and testing of translating name= in UI strings, I have no objection to that. The current l10n process does not generate indexes for UI files (at least I have not found it). The current l10n process generates indexes for xhp files (help), but only partly (because the build system have not been updated and script seems to have been called manually in the sun days), and expect the translator to translate the tree file, with exact the name as used in name=. The last part (name == name=) is a very hard demand, and maybe not the first part you should do when starting on a new language. And on top of it there seems to be problems with utf8 characters (>128), at least I can see the scripts does not always generate what you would expect. So my message was simply, get the main translation done (UI) without considering <...> and then later do the refinements, instead of doing it all, and have a broken system. just my 2ct. rgds jan I. > -- > DiGro > ___________________________ > Apache OpenOffice 3.4 (Dutch) and scanned with Ziggo extended security > (F-Secure) > > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > l10n-unsubscribe@openoffice.**apache.org<[email protected]> > For additional commands, e-mail: > [email protected].**org<[email protected]> > >
