From kde-i18n-doc  Mon Jun 17 08:45:03 2019
From: Chusslove Illich <caslav.ilic () gmx ! net>
Date: Mon, 17 Jun 2019 08:45:03 +0000
To: kde-i18n-doc
Subject: Re: Moving Pology into a Git repository
Message-Id: <201906171045.03309.caslav.ilic () gmx ! net>
X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=156076114209988
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart6554082.v85cSKbC1J"

--nextPart6554082.v85cSKbC1J
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

> [: Luigi Toscano :]
> Should we think about a way for decoupling the language-specific rules
> which may not be generic enough to end up in the global repository, and
> move them to a separate repository, or is it fine as it is now?

To me it is fine as it is now. I also intended it from start to be as
specific as needed, by language and by project. Currently there are
language- and project-specific rules, dictionaries and even code. This
should all arrive together and be ready to use as soon as Pology is
installed.

The only problem may be (as identified once by Pino) that these language-
and project-specific parts may need to be also user-specific. That is, for a
system-wide installed fixed Pology release, that a user can update to the
latest rules, dictionaries, etc. or modify and add them by oneself. But to
support this some more development would be needed.

=2D-=20
Chusslove Illich (=D0=A7=D0=B0=D1=81=D0=BB=D0=B0=D0=B2 =D0=98=D0=BB=D0=B8=
=D1=9B)

--nextPart6554082.v85cSKbC1J
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAl0HUw8ACgkQMSGXgigGr3Gt2QCdGjTsVnmo301kbQwAw5N2JGfW
O/oAoJcsS+v3hvIPysHMMnEviPnSxhZK
=v+cf
-----END PGP SIGNATURE-----

--nextPart6554082.v85cSKbC1J--