- do not use gb_UnpackedTarball_copy_header_files for boost
- adapt the optimization in concat-deps.c for new path
- use boost_headers in all LinkTargets that require it
- add explicit include paths to mysqlc, mysqlcppconn, libvisio, liborcus
Change-Id: I0c43e73ed43cc9d2e6bce8faf55e992d655a0bb9
While 'Kazakh' can be written as 'Kazak' or 'Qazaq', the 'Kazakh' form
is the most widespread according to online sources (Wikipedia,
LCID list from Microsoft). Also the 'Kazakh' form is preferred by a
Kazakh contributor, see http://listarchives.libreoffice.org/global/l10n/msg05444.html
In LibreOffice both 'Kazak' and 'Kazakh' was used at different places.
Change-Id: Ief83eb05e92af16cb5b795f2bbb1e3d6f7c9659a
Doing word-count by switching per-word between two different
kinds of word iterator was insanely slow. This preserves an
ICU break-iterator for each type of word-breaking.
Various places use an empty locale or string to indicate different
meanings and/or variants of "this is not a real locale but I didn't know
what to use else" or abuse LANGUAGE_DONTKNOW in one or the other way. In
preparation of changing that awkward situation now offer the ISO 639
codes for multiple languages [mul] and language undetermined [und],
mapping to LANGUAGE_MULTIPLE and LANGUAGE_UNDETERMINED.
Change-Id: I687de23ffc00a9a056f2837b024e0a62658e3df2
For "simple" known (to us) locales avoid the overhead of liblangtag,
also in preparation of not having to initialize its database during
startup.
This also enables recognition of the 'qtz' pseudolocale for key ID
resources again, see fdo#57413
Change-Id: Id52a1ddc37b42063e3bf68a6dbeaeacfbfa704ef
Changes to commit a81a9109ed43e0b3880c9bd88e58f2b21065226b
The ..._CONGO identifier and "... (Congo)" resource string changes are
only to match the current convention that if a locale is not of the
default country of a language we mention the country. This helps in case
we later add the other locale of a language. Having two Lang-IDs then
with different sublanguage and adding the ISO locales is good practice.
For axk-CG it should be LANGUAGE_USER_YAKA_CONGO instead of
LANGUAGE_USER_AKA and the resource string should be "Aka (Congo)",
because it is not the default axk-CF (Central African Republic), see
http://www.ethnologue.com/show_language.asp?code=axk
For kng-CG it should be LANGUAGE_USER_KIKONGO_CONGO instead of
LANGUAGE_USER_KIKONGO and the resource string should be "Kikongo
(Congo)", because it is not the default kng-CD (Democratic Republic of
the Congo), see http://www.ethnologue.com/show_language.asp?code=kng
However, changed name to Koongo instead of Kikongo because that is the
default name even for Congo, see
http://www.ethnologue.com/show_language.asp?code=kng, and used
LANGUAGE_USER_KOONGO_CONGO instead.
For njy-CG it should be LANGUAGE_USER_NJYEM_CONGO instead of
LANGUAGE_USER_NJYEM and the resource string should be "Njyem (Congo)",
because it is not the default njy-CM (Cameroon), see
http://www.ethnologue.com/show_language.asp?code=njy
For puu-CG it should be LANGUAGE_USER_PUNU_CONGO instead of
LANGUAGE_USER_PUNU and the resource string should be "Punu (Congo)",
because it is not the default puu-GA (Gabon), see
http://www.ethnologue.com/show_language.asp?code=puu
For yom-CG it should be LANGUAGE_USER_YOMBE_CONGO instead of
LANGUAGE_USER_YOMBE and the resource string should be "Yombe (Congo)",
because it is not the default yom-CD (Democratic Republic of the Congo),
see http://www.ethnologue.com/show_language.asp?code=yom
For each of these ..._CONGO lang-IDs introduced the default ID and made
the ..._CONGO ID with sublanguage 0x20, adapted corresponding IDs in
*.xml files.
All IDs in those *_CG.xml files needed to be corrected anyway as they
all had a replaceTo="[$CFA-63A]" copied from sg_CF.xml, the ID needs to
match that of the LangID instead.
As all LC_FORMAT element section were identical, made them refer to
kng_CG instead of having duplicated copies, same for LC_CURRENCY.
Removed the executable permission bits from *_CG.xml files.
Change-Id: Iae06af5fbf19e3a3c83a4f4b4dcb857213df629e