2009/9/18 Ain Vagula :
> 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
That is so right, Ain. But obviously it is easier if 100 translators
2009/9/18 Ain Vagula :
> hcshared22 also introduced a lot of needed changes about new or
> changed features in 3.1, so we cannot use older source here.
This is something I proposed here but my idea was not accepted well.
I proposed that help changes would come in smaller packages that would
be ea
André Schnabel wrote:
> 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 no
Ain Vagula wrote:
and the worse of all is that we already wasted 2 weeks, waiting
hcshared23 which didnt fix much...
IIRC, we rolled back around 900 changes menuitem > emph and
insignificant spaces. The rollback was complicated
because there was only little time to do it and we needed
to make s
Martin Srebotnjak wrote:
2009/9/18 Ain Vagula :
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
That is so right, Ain. But obviously it is easier i
Ok, this number is good to know. I apologize. Translator sees all
changes as fuzzy, seems like I have to rollback in cvs a bit and do
merge again against m59
ain
On Fri, Sep 18, 2009 at 11:06, Frank Peters wrote:
> Ain Vagula wrote:
>>
>> and the worse of all is that we already wasted 2 weeks, w
2009/9/18 Frank Peters :
> Ain Vagula wrote:
>>
>> and the worse of all is that we already wasted 2 weeks, waiting
>> hcshared23 which didnt fix much...
>
> IIRC, we rolled back around 900 changes menuitem > emph and
> insignificant spaces. The rollback was complicated
> because there was only litt
Hi,
> Von: Mathias Bauer
>
> Why another CWS? Couldn't we use the same? And if we did it with
> Mercurial instead of svn it would be easy to handle: provide a
> repository on services.openoffice.org that everybody can clone and where
> changes could be pushed to.
"Translators" are not develope
Martin Srebotnjak wrote:
2009/9/18 Ain Vagula :
hcshared22 also introduced a lot of needed changes about new or
changed features in 3.1, so we cannot use older source here.
This is something I proposed here but my idea was not accepted well.
I proposed that help changes would come in smaller
Martin Srebotnjak wrote:
2009/9/18 Frank Peters :
Ain Vagula wrote:
and the worse of all is that we already wasted 2 weeks, waiting
hcshared23 which didnt fix much...
IIRC, we rolled back around 900 changes menuitem > emph and
insignificant spaces. The rollback was complicated
because there wa
2009/9/18 Frank Peters :
> Are you saying that *none* of those rollback changes are in m59?
>
> Like I wrote in my other response that was complicated
> since we had to make sure not to touch anything that already was
> localized before m56.
Well, Frank, some were, but others remained, like the on
Hi Frank,
Original-Nachricht
> Von: Frank Peters
> > Namely, I have seen that also changes in English strings are a bit
> > frustrating for us non-English localizers - in English strings
> > sometimes just fixing a typo makes the string in your language fuzzy,
> > but actually
Martin Srebotnjak wrote:
2009/9/18 Frank Peters :
Are you saying that *none* of those rollback changes are in m59?
Like I wrote in my other response that was complicated
since we had to make sure not to touch anything that already was
localized before m56.
Well, Frank, some were, but others r
On 09/18/09 11:01, Andre Schnabel wrote:
Hi Frank,
Original-Nachricht
Von: Frank Peters
Namely, I have seen that also changes in English strings are a bit
frustrating for us non-English localizers - in English strings
sometimes just fixing a typo makes the string in your l
Hi,
> Von: Uwe Fischer
>
> this flag means "this paragraph is irrelevant for translations" or
> "never translate this paragraph". I did not know that this does not get
> passed over to translators, though. Bad tools design :-(
>
> What we would need is a flag that says "the changes to this p
Hi everyone.
A new page was added (15 January) to the BASIC Guide in the Wiki. So
far it has been translated to Hungarian and Italian. Translations
missing are:
French
Japanese
Chinese
to cover the languages that this guide has been translated to in the Wiki.
Is someone from each of t
A new extension has been added to the OpenOffice.org Wiki that may be of
some help to those of you who are involved in translating
documents/pages in the Wiki.
The extension is called WatchSubPages, and it allows you to put a watch
on an entire subpage structure in one step (instead of adding a wa
Hi Clayton.
Thank you for this notice.
I am going to translate with Japanese translation team:)
On Fri, 18 Sep 2009 13:17:09 +0200
"ccornell - OpenOffice.org" wrote:
> Hi everyone.
>
> A new page was added (15 January) to the BASIC Guide in the Wiki. So
> far it has been translated to Hungar
Hi Rafaella, Aijin.
Can we translate this on new Pootle?
It seems good time for try new pootle if it can use already.
On Fri, 18 Sep 2009 23:00:41 +0900
Makoto Takizawa wrote:
> Hi Clayton.
>
> Thank you for this notice.
> I am going to translate with Japanese translation team:)
>
> On Fri, 1
Hi all,
So do I.
I'd also like to know whether we can work on pootle.
Thanks in advance.
2009/9/18 Makoto Takizawa :
> Hi Rafaella, Aijin.
>
> Can we translate this on new Pootle?
> It seems good time for try new pootle if it can use already.
>
> On Fri, 18 Sep 2009 23:00:41 +0900
> Makoto Takiz
20 matches
Mail list logo
