On Mon, Sep 5, 2011 at 8:08 PM, Christoph Noack <christoph@dogmatux.com>wrote:
Oh, let's simply keep the new string if it fits from you point-of-view.
My main aim was to hint towards existing information that might have
been helpful here.
Concerning the latter, it would be great if you could CC the mailing
list libreoffice-ux-advice if (hard to discuss) string proposals pop up.
Maybe we/I can provide hints to discussion from OOo UX times.
Well, the discussion on l10n list was quite short. I didn't see anyone
replying and just moved forward. I'll remember you hint about terminology,
but I don't think it a common issue for the l10n list, except in cases no
one knows how to translate something.
Since I have another question, I'd like to move that discussions to that
mailing list (no subscription required) and like to ask you, whether a
terminology database / glossary is available for UI stuff. Is this
something the l10n team is working on? Terminology is terribly important
and it would be immensely helpful for UX / UI stuff to have a shared
resource for Documentation / Translation / Design.
I reduced to CC list to the ux list. I'm not that involved with translation
in general (mainly focused on Hebrew). I'm not aware of any db for glossary
inside the project. There's probably a general one (cross open source
projects) for some of the languages.
For Hebrew, I have two guys trying to keep some consistency between the open
source projects.
Kaplan
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.