On 12/20/2011 3:15 PM, drew wrote:
On Wed, 2011-12-21 at 00:04 +0100, André Schnabel wrote:
Hi,
Am 19.12.2011 13:38, schrieb Rob Weir:
On Mon, Dec 19, 2011 at 12:39 AM, Dwayne Bailey<[email protected]> wrote:
Small teams, small number of people wanting to make sure that OOo in
whatever form is localised. The strings are almost 100% the same, at the
moment, between AOO and LibO. So how to share resource between the two.
I don't want to waste people time translating the same thing twice. I also
want to make sure that the translations are consistent no matter where it
was translated, so sharing for consistency is important to me.
So the one issue is logistics of doing this, the other is the licensing
concern.
I don't think that we can avoid having a divergence in translation
strings. New features added to LO will differ from new features added
to AOO.
I need to agree here - actually LibO has several features that AOO does
not have. But LibO UI has undergone some string changes as well - so you
even won't get 100% translation if you apply LibO translations to AOO.
But the underlying terms we use to describe the UI and the
basic application features will remain the same. Terms like "pages",
'sections", "sheets" and 'fonts" etc., are not going to change. So in
that case, would a shared translation memory database help?
The setup at OOo was, that the full po repository was the translation
memory. You seem to mix that with the glossary (which defines terms).
TM and glossary might seem similar for UI, as UI string segments are
normally rather short. Unfortunately - due to the complexity of the
software - the UI strings allone can hardly be used as translation
memory - they need to be accompanied with context information (location
in the code files).
e.g. Sheet has at least three different german translations, same with
font.
regards,
Hi André
thanks for your explanations.
I'm still left, as a bystander when it comes to the translations, with
one simple question.
What happened to the pootle server at OO.o?
As I mentioned before [1], that server is in the possession of TOO.
Andrew
[1]
http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201112.mbox/%[email protected]%3E
Someone has to know.
//drew
--
Andrew Rist | Interoperability Architect
OracleCorporate Architecture Group
Redwood Shores, CA | 650.506.9847