On 7/30/13 3:35 PM, janI wrote: > On 30 July 2013 15:03, Rob Weir <[email protected]> wrote: > >> On Tue, Jul 30, 2013 at 3:33 AM, Jürgen Schmidt <[email protected]> >> wrote: >>> On 7/30/13 9:05 AM, janI wrote: >>>> On 30 July 2013 08:30, Jürgen Schmidt <[email protected]> wrote: >>>> >>>>> On 7/29/13 3:21 PM, janI wrote: >>>>>> On 29 July 2013 15:05, Jürgen Schmidt <[email protected]> wrote: >>>>>> >>>>>>> On 7/29/13 2:24 PM, Christos Stefanidis wrote: >>>>>>>> Please see the below request from a volunteer, could we add the po >> 4.0 >>>>>>>> files for >>>>>>>> Ukrainian on pootle? >>>>>>> >>>>>>> yes, I will work on this >>>>>>> >>>>>> >>>>>> Will you do that in 4.0, I would suggest we setup 4.01 (not 4.1) and >> make >>>>>> the other project RO. >>>>> >>>>> I don't think so, I would prefer to continue on the current project for >>>>> simplification reasons. >>>>> >>>>> A 4.0.1 will contain fixes only and no new UI elements. And corrected >> or >>>>> further translation, I see no demand for a new translation project on >>>>> Pootle. But we should of course bring all languages in sync with the >>>>> latest templates. Means merge what we have against the latest templates >>>>> of AOO 4.0 (a lot of work that I don't have at the moment) >>>>> >>>>> >>>>>> >>>>>> Should we also use the time now, to coordinate >>>>>> languages defined in AOO <-> sdf files <-> pootle files >>>>>> >>>>>> so we have a consistent set, that would make my upgrade work easier. >>>>>> >>>>> >>>>> I am not sure if I understand what you mean exactly. Can you explain it >>>>> in detail please. >>>>> >>>> >>>> Currently we have sdf files, not converted to po files (present in >> pootle >>>> server). >>>> >>>> We also have po files in pootle at least not synchronized with the sdf >>>> files (or in some cases the sdf files does not exist). >>>> >>>> We should have >>>> 1) source consistent with sdf (extract) >>>> 2) sdf files consistent with pootle server >>>> >>>> "just" as sync. job, but important. >>>> >>>> Today, when I run test, I have to use sdf for some part, po files for >>>> other, and in the cases where there are conflict, I have to guess what >> is >>>> right. >>> >>> Ok I see and understand and I am not sure how we should handle this >>> best. Having all sdf synchronized to current templates and available as >>> po files would be good. On the other hand we want active translation >>> communities only and the question is if we should add them on demand or >>> simply because there is an sdf file already. >>> >>> In general I would tend to synchronize all but I would like to avoid >>> overhead as well. If there is nobody working on a language it will take >>> our time to work with this files for nothing. >>> >>> What do others think? Should we focus on active languages and add >>> further languages on demand only? Or should do a one time shot and >>> synchronize all to remove the sdf files and have everything as po files >>> as part of Jan's work. >>> >> >> Having all the languages in Pootle makes it easier for potential >> volunteers to see what is already started and how much more work is >> needed. So it could be useful. But I'd probably avoid any >> unnecessary changes in the 4.0 project. We want to keep that stable >> in case we do a 4.0.1 releases. In other words, I consider that 4.0, >> in Pootle and in SVN, is still in Release Blocker only mode. Of >> course, the trunk is the Wild Wild West.
Well it depends how you see it, Imacat for example worked on Pootle to complete the translation for zh-TW and other fixed problems in their language. I would see Pootle as tool only that help us to get an overview where we are and that translators can use to do their work. Comparable to an editor. We can easy rename the 4.0 project to the next coming release or 4.x and can continue to work with them. We will take regular snapshots (TBD) and continue this into svn. The only release relevant source is in svn. I have added Ukrainian Juergen >> > > Pootle server should ideally be a copy of trunk, it we want to freeze > pootle server, then the way forward is to make a new project (pretty > simple) e.g. 4.01 or 4.0full. > > rgds > jan I. > >> >> -Rob >> >> >>> Juergen >>> >>> >>>> >>>> rgds >>>> jan I. >>>> >>>> Juergen >>>>> >>>>> >>>>>> have a nice day >>>>>> rgds >>>>>> jan I. >>>>>> >>>>>> >>>>>>> >>>>>>> Juergen >>>>>>> >>>>>>>> >>>>>>>> /Christos. >>>>>>>> >>>>>>>> >>>>>>>> ---------- Forwarded message ---------- >>>>>>>> From: Roman Kononenko (Confluence) <[email protected]> >>>>>>>> Date: Mon, Jul 29, 2013 at 3:13 PM >>>>>>>> Subject: [CONF] Apache OpenOffice Community > Localization >> Volunteers >>>>>>>> To: [email protected] >>>>>>>> >>>>>>>> >>>>>>>> Localization >>>>>>>> Volunteers< >>>>>>> >>>>> >> https://cwiki.apache.org/confluence/display/OOOUSERS/Localization+Volunteers?focusedCommentId=33297753#comment-33297753 >>>>>>>> >>>>>>>> Page >>>>>>>> *comment added* by Roman >>>>>>>> Kononenko<https://cwiki.apache.org/confluence/display/~rkononenko> >>>>>>>> >>>>>>>> Hi I would like to help translate OO 4.0 into Ukrainian, but it >> seems >>>>>>> like >>>>>>>> there's only 3.4 version at the moment available for >>>>>>>> Ukrainian. What steps do I need to take in order to add Ukrainian >> here >>>>> - >>>>>>>> https://translate.apache.org/projects/aoo40/ >>>>>>>> >>>>>>>> Stop watching >>>>>>>> page< >>>>>>> >>>>> >> https://cwiki.apache.org/confluence/users/removepagenotification.action?pageId=29130766 >>>>>>>> >>>>>>>> | Change email notification >>>>>>>> preferences< >>>>>>> https://cwiki.apache.org/confluence/users/editmyemailsettings.action >>> >>>>>>>> View Online< >>>>>>> >>>>> >> https://cwiki.apache.org/confluence/display/OOOUSERS/Localization+Volunteers?focusedCommentId=33297753#comment-33297753 >>>>>>>> | >>>>>>>> Reply >>>>>>>> To This< >>>>>>> >>>>> >> https://cwiki.apache.org/confluence/display/OOOUSERS/Localization+Volunteers?replyToComment=33297753#comment-33297753 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>> For additional commands, e-mail: [email protected] >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
