Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi Andre,

On Fri, 2011-01-07 at 11:32 +0100, Andre Schnabel wrote:
I'd guess both are side-effects of removing the localized templates :(

        Right; of course - we could add another 100Mb of duplicate templates to
the windows installer to fix this ;-)

I currently have no idea how to fix this quickly, but imho stopper for
localized versions of LibO (did not file an bug yet).

        Well - at this stage, we're in some serious code lock-down; and these
don't look like easy fixes; so we have some options:

        * make the installer 100Mb bigger
        * delay the release by a month+
        * ship with nom-localised templates names

        It is -possible- that we can fix the most annoying "document set to the
wrong locale" issue, in some more sensible way - by removing whatever
hard-coded locale nonsense is in the existing templates: presumably this
is possible - and susceptible to l10n help - if we can do that it should
be easy to edit that out of the templates.

        Wrt. the non-localised names I'd like to fix them for the next point
release, which should be only a few weeks after the first point-zero
release. I've created a new tracking bug for 3.3.1 here:

        https://bugs.freedesktop.org/show_bug.cgi?id=32894

        And made this bug block it,

        Thoughts ?

                Michael.

-- 
 michael.meeks@novell.com  <><, Pseudo Engineer, itinerant idiot



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.