-----BEGIN PGP SIGNED MESSAGE-----
Am 28.04.2016 um 13:01 schrieb toki:
On 27/04/2016 23:30, Dennis Roczek wrote:
@toki I really hope not that the maintainers do have *NOT* to learn g
It should be more than an intelligent pootle system.
The reason I mentioned GIT, is because there was (operative word _was_
a group of people working on an extension for AOo/LibO to save documen
to GIT. The projected end result would be that all the individual woul
have to know about GIT, was to click on this extension to either save,
or retrieve the document from GIT.
there are still some projects, like the en_US or the en_GB dictionary.
looks with the affix files, but we will find somebody who can do it -
My impression is that there is a python library that takes word lists,
and creates affix files from them.
If the "TDF" and volunteers are able to implement that in a technical
way, Will be a completely different story.
Listing the technical requirements for the must-haves and nice-to-have
Yeah, I think easiest would be to start to create a wiki page listing
* pro and Cons
* could be added later
stuff (mostly features). Technical requirement mostly depends on the
implementation (e.g. phyton as mentioned above).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: 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