Implementing accessibility non-regression check tool
erack at redhat.com
Wed Feb 28 16:27:43 UTC 2018
On Wednesday, 2018-02-28 10:42:07 +0100, Miklos Vajna wrote:
> If I focus on maintenance, I would just use the same XML parsing
> infrastructure that we use everywhere else for file import purposes, and
> the checker would be in C++. We do report line and column numbers when
> ODF import fails at a specific location.
> But I didn't want to suggest a rewrite if you decided to go with Python
> for some reason.
The initial reason (correct if I'm wrong) was that the checker could be
used standalone and work on any glade .ui file, not even related to
LibreOffice, and thus be used by any project to raise a11y awareness.
LibreOffice Calc developer. Number formatter stricken i18n transpositionizer.
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
Care about Free Software, support the FSFE https://fsfe.org/support/?erack
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: not available
More information about the LibreOffice