Hi Sophie,
On 2010-12-28 at 14:30 +0300, Sophie Gautier wrote:
It may be quite hard to make difference between a *new* (m90) translated
string and an old one.
This is why I ask: do we merge Libo with the last dev versions or do we
work on the last SDF file only (I think it's OOo330m9)
Hi Kendy,
On 29/12/2010 19:21, Jan Holesovsky wrote:
Hi Sophie,
On 2010-12-28 at 14:30 +0300, Sophie Gautier wrote:
It may be quite hard to make difference between a *new* (m90) translated
string and an old one.
This is why I ask: do we merge Libo with the last dev versions or do we
work
Hi,
I keep localizing OOo on my computer, with regular updates, knowing or
hoping that at this stage most of changes for OOo 3.4 will make it to LO
3.4. Later, when all files are merged (OOo sdf + lo-build) into a LO set of
po files, I can center on localizing those only.
Lp, m.
2010/12/29
Hi Sophie,
On 2010-12-29 at 19:52 +0300, Sophie Gautier wrote:
But we need to merge the strings quiet soon now because we didn't have
the opportunity any more to fix l10n issues in OOo 3.3 since
I am confused - did you mean 3.4 here, or I did not understand your
initial mail, please?
Thank
Hi Sophie,
On 2010-12-29 at 19:52 +0300, Sophie Gautier wrote:
This is why I ask: do we merge Libo with the last dev versions or do we
work on the last SDF file only (I think it's OOo330m9) because it is now
two completely separated products?
We are still working towards a plan how to
On 29/12/2010 20:25, Jan Holesovsky wrote:
Hi Sophie,
On 2010-12-29 at 19:52 +0300, Sophie Gautier wrote:
But we need to merge the strings quiet soon now because we didn't have
the opportunity any more to fix l10n issues in OOo 3.3 since
I am confused - did you mean 3.4 here, or I did not
Hi Kendy,
On 29/12/2010 20:31, Jan Holesovsky wrote:
Hi Sophie,
On 2010-12-29 at 19:52 +0300, Sophie Gautier wrote:
This is why I ask: do we merge Libo with the last dev versions or do we
work on the last SDF file only (I think it's OOo330m9) because it is now
two completely separated
