Re: [Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters

Caolán McNamara <caolanm -AT- redhat.com>
Mon, 04 Apr 2011 16:23:06 +0100

On Sun, 2011-04-03 at 17:00 +0200, archlid wrote:

Is pyAltFCFGMerge supposed to replace the Java merging program? 
I read that the Java dependencies will be reduced in LibreOffice.


I wrote it a long time ago as basically a direct copy and paste and
re-word version of the java one when I was trying to port to something
that didn't have any working java IIRC. It gets used alright with
--disable-java, I'm not 100% sure that it still works perfectly, but it
munges together the config "fragments" in
filter/source/config/fragments/ to make the list of filters that
LibreOffice shows in file->open, save as, etc. 

So it precedes the "reduce java dependencies" plan, but I guess it could
be made part of it.

C.

Context

[Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters · archlid
- Re: [Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters · archlid
  - Re: [Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters · Michael Meeks
    - [Libreoffice] [PUSHED] Python 3 compatibility for build tools + unicode support for filters · Michael Meeks
  - Re: [Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters · Caolán McNamara
    - Re: [Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters · Michael Meeks
      - Re: [Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters · Andreas Becker

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.