https://bugs.documentfoundation.org/show_bug.cgi?id=99579
V Stuart Foote <vstuart.foote@utsa.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS|Windows (All) |All
--- Comment #4 from V Stuart Foote <vstuart.foote@utsa.edu> ---
Prefer Bugzilla submissions in English of course, but a legitimate question and
we knew what was being asked so felt no need to invalidate, nor to provide a
translation.
Admittedly I depend on the good folks at Google myself, but their gisting
translation gets further corrupted by a couple of typos/abbreviations in the
French as submitted.
I have adjusted this to be the localization enhancement it is.
Question though would be how best to accomplish this. If localized flavors of
the sample documents/templates are generated by the project (as ODF templates),
we probably will want to move them out of the core packaging.
But where, should they move? Into the offline help packages? Or do we get into
the extension business, to better accommodate the asymmetrical localization
efforts that will result.
And of course if done, someone under the ESC will have to coordinate the
efforts. Sophie coordinates the Pootle based translation efforts now, this
effort is completely out of scope to that.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 99579] bundled sample document templates are in english only, can we localize · bugzilla-daemon
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.