and the worse of all is that we already wasted 2 weeks, waiting hcshared23 which didnt fix much... to be exact I wasted 2 months because I didnt know what to do with changes since July 9th.
ain On Fri, Sep 18, 2009 at 09:22, Ain Vagula <[email protected]> wrote: > hcshared22 also introduced a lot of needed changes about new or > changed features in 3.1, so we cannot use older source here. > I believe that there is no time any more to select out unwanted changes. > When we ignore unwanted changes because we dont want to handle about > 2000 strings twice, the quality of translated help in 3.1 will be > worse than ever. If we decide fix the translation, we may run out of > time. Anyways, it does not harm, when img-strings are fuzzy, default > pictures are mostly same in all languages so the fallback displays the > same. It makes the count of strings that need attention a bit smaller. > > ain > > 2009/9/18 André Schnabel <[email protected]>: >> Hi, >> >> Mathias Bauer schrieb: >>> >>> Correct me if I'm wrong, but wouldn't it be possible to provide a custom >>> build that contains the rollback changes that didn't make it into >>> m59/m60? Translators could use this one instead of the milestone build. >>> >> >> We do not translate "builds" we translate "source". So a custom build would >> not help. >> >> To map the idea to source code, we would need a special CWS, that rolls back >> the changes - and we would need to have another cws to hold translations >> for the "Rollback CWS" ... seems to be a little complicated procedure to me. >> (At the other hand this is quite similar to what the documentation team just >> tried). >> >>> Sorry in advance if that is a bad idea for some other reasons that my >>> tiny little brain doesn't know. :-) >>> >> >> It's friday - you are excused ;) >> >> André >> >> --------------------------------------------------------------------- >> 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]
