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


Khaled Hosny, on sam. 24 févr. 2018 01:02:29 +0200, wrote:
On Thu, Feb 22, 2018 at 04:13:42PM +0100, Samuel Thibault wrote:
Stephan Bergmann, on jeu. 22 févr. 2018 15:49:40 +0100, wrote:
That means external/lxml will need to:

* build against and run with either the system Python or the locally-built
one from external/python3,

* build against and run with either the system libxml2/libxslt or the
locally-built one from external/{libxml2,libxslt}.

That's four different ways how to build external/lxml, and slightly more
different ways (using the system lxml versus external/lxml) how to run the
gla11y tool in solenv/gbuild/UIConfig.mk.  And getting all those ways to
work, on the different platforms, will be hell.

Well, python, libxml2 and libxslt are very-well-established projects
with a huge lot of reverse dependencies, and thus they have to take
backward compatibility into extremely careful consideration. I thus
don't fear too much problems building lxml against various versions of
them.

(and the current building issue reported in gerrit 50115 is merely that
the current LO python3 module doesn't install any header file or such)

Isn't there another option to make that gla11y tool process XML data, one
that better matches LO's needs?

Well, we can reimplement the world for sure.

“import xml.etree.ElementTree as ET” (which is part of Python standard
library) not good enough?

“
An issue with these is that they do not keep source line numbers of the
nodes.  That's really concerning for providing useful information to
the programmer.  We will be bothering them with new warnings that they
will have to learn about ; if we don't provide with line numbers, they
will get rightfully angry :) We could fallback to only providing the
class and id of the suspected widget. In some cases we have seen no id
defined, and thus no pointer to give to the programmer.
”

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.