-----BEGIN PGP SIGNED MESSAGE-----
but that's the whole point: getting the actual system easier and include
I have no clear understanding which languages uses which kind of system
and scripts. But as far as I know: many who uses scripts to get the
extensions packed, simply use homegrown / self-made scripts in any
language or simply pack the extension manually.
Do try to get the system running, provide a system (hosted / maintained
by TDF) and everybody would use the same system to create new
dictionaries - it will become superior after time. Additional systems
(e.g. Mozilla based products for the easiest example) can be added later
The point about the affix file: I imagined the system more on a much
lower base: Joe Average is computer affine and realized that the system
is based on volunteer work and sends his "customs"/unknown words to the
maintainer (either e.g. a web page, directly integrated within
libreoffice or whatever) and the maintainer (similar to the Language
Administrator in Pootle) decides if it goes in the dictionary or not.
@toki I really hope not that the maintainers do have *NOT* to learn git.
It should be more than an intelligent pootle system. (dunno how that
looks with the affix files, but we will find somebody who can do it - if
Moreover: that kind of system won't include that much resources (neither
human resource nor server source) to maintain. OTOH we might have
additional many new easy hacks for new developers who want to develop
new "skripts" to create extensions for other plugins or conversations to
other dictionary systems, or the like.
At the moment this is only a discussion if "we" find that useful. If the
"TDF" and volunteers are able to implement that in a technical way, Will
be a completely different story.
Am 27.04.2016 um 23:40 schrieb Michael Bauer:
Sgrìobh Dennis Roczek na leanas 25/04/2016 aig 15:33:
If the maintainers are not responsive (or if the dictionary is
abandoned), we actually cannot do anything as long as we have no new
maintainer for a fork. If there is somebody willing to overtake the
development, then forking of that particular dictionary is indeed a
A couple of extra thoughts from an active maintainer of a dictionary a
the associated extensions.
In general, I'm interested in anything that brings together scattered
resources and makes stuff more user friendly, be that end users or dev
- there would have to be some sort of a locale-specific admin system f
active maintainers joining. Crowdsourcing stuff works in big languages
but if folk start submitting random stuff to a locale like Scottish
Gaelic or playing with the affix file, that's a recipe for disaster.
- there are different ways in which people maintain their dictionaries
Some edit the text file directly, others build from corpora, in our
case, we use scripts to build from a dictionary database, which
automatically generates the .zip/.oxt/.xpi files. One would probably
have to consider different entry points if ones were to successfully
attract people from different projects because I would NOT want to hav
to start manually maintaining our file.
- one thing that hasn't been mooted yet would be making some provision
for easily creating new dictionaries for new locales, something that h
a loc-tech threshold.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
To unsubscribe e-mail to: email@example.com
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