not that is is urgent I won't update the sources, but I noticed new problems
Error: Translation Tag Missmatch, Line 103414, UniqueID helpcontent2/source\text\swriter\main0205.xhp/help/par_id3147578/2//: Missing Tag in Translation: \</ahelp\> at Position 344 "�ог обекта у Писцу и Рачуну. Изаберите мени Приказ - Палете алатки - Својства графичког објекта. Контроле су укључене када је графички објекат изабран. По подешеност�" Error: Translation, Line 103420, UniqueID helpcontent2/source\text\swriter\main0206.xhp/help/par_id3154277/2//: Expected Symbol: Close tag for \<ahelp hid=\"HID_NUM_TOOLBOX\"\> at Position 0 "" Error: Translation Tag Missmatch, Line 103420, UniqueID helpcontent2/source\text\swriter\main0206.xhp/help/par_id3154277/2//: Missing Tag in Translation: \</ahelp\> at Position 230 "elp hid=\"HID_NUM_TOOLBOX\"\>Трака за \<emph\>набрајање и нумерисање\</emph\> садржи функције за измену структуре нумерисаних пасуса, укључујући мењање редоследа пасуса и дефинисање �" Juergen On 9/11/13 5:20 PM, Jürgen Schmidt wrote: > On 9/11/13 3:04 PM, Rob Weir wrote: >> On Wed, Sep 11, 2013 at 5:12 AM, Jürgen Schmidt <jogischm...@gmail.com> >> wrote: >>> On 9/10/13 8:20 PM, Vladislav Stevanovic wrote: >>>> Hi Jürgen, >>>> Can you tell me where is problem? I can not find bugs, so if there exist >>>> some method for checks, please tell me, to avoid problems in future. >>> >>> I have fixed it already. It were mainly missing tags or mismatched xml. >>> Just try to double check before you commit if the tags are matching. >>> Means an open tag have the related closing tag. And the ids in tags are >>> not changed for example. >>> >>> I believe Pootle gives a hint if xml tags are not matching, in this >>> cases just double check ... >>> >> >> This is a manual, error-prone process that will always be a subject to >> human error. I don't think being more careful is going to help much. >> It certainly won't reduce the error rate to zero. We really need >> tooling in this area, that every translator can run for themselves, to >> report the errors, so they can be fixed before the translation >> deadline. >> >> Imagine if developers did not have compiler errors on the desktops and >> had to wait for feature freeze to get a list of errors? >> >> If Pootle has an easy way to report these problems, then that is great. > > I agree and my hope was that we can do something in this area with the > new tooling. > > The whole conversion of po to sdf is error prone and that is why we want > to eliminate this conversion step > > Juergen > >> >> -Rob >> >>> Juergen >>> >>> >>>> Thanks in advance, >>>> Wlada >>>> >>>> >>>> 2013/9/10 Jürgen Schmidt <jogischm...@gmail.com> >>>> >>>>> Hi, >>>>> >>>>> I noticed several problems in the started help translation for Serbian. >>>>> >>>>> Please be careful and check the tags in brackets <>. An often and >>>>> typical error is to change tags, miss the closing tag or miss tags at >>>>> all. Please double check before you commit. This will help to avoid a >>>>> lot of post processing work. >>>>> >>>>> Thanks >>>>> >>>>> Juergen >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org >>>>> For additional commands, e-mail: l10n-h...@openoffice.apache.org >>>>> >>>>> >>>> >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: l10n-h...@openoffice.apache.org >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: l10n-h...@openoffice.apache.org >> > --------------------------------------------------------------------- To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org For additional commands, e-mail: l10n-h...@openoffice.apache.org
