Fixing the original English strings

l10n
#1

Hi,

Von: Kohei Yoshida
Gesendet: 03.11.10 14:45 Uhr

I've found some inconsistent English strings that I'd like to fix. But
I thought I would ask here first since I don't really know how our
translation framework works.

fine with me, as long as it affects the lo-bild.po files only.

If we speak about strings that are covered by OOo translations - please do
*not* do massive changes.
We do not have a translation process in place. So you would change from
"inconsistent english but localized" strings to "consistend english but
non-localized" strings.

please let's wait with such changes for 3.4 (or the time we know how to
handle full translations).

regards,

André

#2

2010.11.03 17:04, Andre Schnabel rašė:

I've found some inconsistent English strings that I'd like to fix. But
I thought I would ask here first since I don't really know how our
translation framework works.

fine with me, as long as it affects the lo-bild.po files only.

If we speak about strings that are covered by OOo translations - please do
*not* do massive changes.
We do not have a translation process in place. So you would change from
"inconsistent english but localized" strings to "consistend english but
non-localized" strings.

please let's wait with such changes for 3.4 (or the time we know how to
handle full translations).

I think this should be reported in our bug tracker, whenever we have one.

Rimas

#3

Hi,

> Von: Kohei Yoshida
> Gesendet: 03.11.10 14:45 Uhr

>
> I've found some inconsistent English strings that I'd like to fix. But
> I thought I would ask here first since I don't really know how our
> translation framework works.

fine with me, as long as it affects the lo-bild.po files only.

Ok. I just changed one string then ("DataForm..." to "Form..." in the
Data menu in Calc). The other strings weren't used until LO 3.3, but
the strings themselves were long in OOo proper, so I'll wait on that
one.

If we speak about strings that are covered by OOo translations - please do
*not* do massive changes.
We do not have a translation process in place. So you would change from
"inconsistent english but localized" strings to "consistend english but
non-localized" strings.

please let's wait with such changes for 3.4 (or the time we know how to
handle full translations).

Understood.

Kohei

#4

So, do we have a string freeze for LO-build-XY.po files for LO3.3 in place?

Lp, m.

#5

I don't think we've hit the string freeze yet, though I don't have the
exact date of string freeze...

Andre?

Kohei

#6

Hi,

So, do we have a string freeze for LO-build-XY.po files for LO3.3 in place?

just briefly discussed this in the SC-call. We might need to intruduce one or two dialoges (we are still looking for a solution for the online help).

Genreal string freeze would be end of this week (but thos very few strings). We have an engineering teem call tomorrow and will have more details then.

Regards,

André