Age | Commit message (Collapse) | Author |
|
Change-Id: I3c5cf65bee50ec0511031b50e1b9f5589491e6bd
|
|
Change-Id: I9ac503b073ee3f9b8e7958264ffcc26d9446c220
|
|
was lost with 2c47c9989e308ddef22066607795eb3feef9f76b
Change-Id: Iee6f2caa2e934ed998c186e12a3f8b433fb64574
|
|
Change-Id: I967b75b54a330692fb88783609e714d016506f89
|
|
|
|
Change-Id: I294c9b665a9314169515fe20b97b4558580662e9
|
|
Change-Id: I4bf7bc4f58bac7675cf694dc206e6ba119a6354e
|
|
Change-Id: Ia2ed3dc0d0e135913c25e1c389326ee3fbc39719
|
|
|
|
|
|
... as it causes problems on Windows:
file:///C:/lo/core/solver/wntmsci12.pro/share/liblangtag%5Clanguage-subtag-registry.xml:709: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xE5 0x6C 0x3C 0x2F
<description>Norwegian Bokmål</description>
Apart from the encoding issue (looks like that language-subtag-registry.xml
delivered from module liblangtag is generated as MS-1252 rather than UTF-8 on
Windows), what also looks worrying in the error message is the backslash encoded
as %5C (and the entity resolving that URL apparently decoding it somewhat
naively).
Change-Id: I756f911a92b144e3732f63668d36b4ae941f975a
|
|
Change-Id: Ic38d0282dba99efe2ecc45142a927ba3d8fa167d
|
|
Change-Id: I97312c746e8a76af73851c474b0c6c2491c44803
|
|
|
|
Change-Id: I157ea5b5b32ca0664c8eec775de01958f7b55f06
|
|
|
|
Change-Id: I292de75fbc5dd83bfeefc242e8ac699ab7b6fad8
|
|
|
|
We don't need GLib then either. For now just a quick dummy replacement
for liblangtag in i18npool that will crash at run-time. Improve once
it starts to get used, and once it is clear what functionality is
needed.
Change-Id: I9777c2c776dd6e479e1d6f0fb073f289ea6ff2f4
|
|
|
|
|
|
Change-Id: I459f7fd097a81ef5977974f52b0cc2c2f155a810
|
|
Change-Id: I9685faf1658bac91abe348a409ec85e2421b1c49
|
|
Change-Id: I263d35464ceaa7374e8ca94f7e72e56ee33aab53
|
|
There can be only one usedInCompatibleFormatCodes="true" and because of
the new symbol with identical ISO 4217 TRY we need also
legacOnly="true" on the old entry. Additionally, as the TL symbol was
already used with TRL also that one needed legacyOnly="true" to not end
up with a list of duplicated TL formats in the number formatter.
Change-Id: I8e3ec2f75828b8f7c6a2077ef2fd30fc5e7a5642
|
|
Turkish currency New Turkish Lira was replaced with Turkish Lira on 01.01.2009.
TRY TL added for default. TRY YTL is not default anymore.
Change-Id: I08f5f70bf46d2f655c11ddaff77f68ba1e398225
|
|
Change-Id: Icd10968e886be1d534e8037db6225e83712384ee
|
|
Change-Id: I11440667bdf73ed09ebc83771acf33e2d3e61f6c
|
|
Change-Id: Ic60f440f8dc8fcfa76a023557e76fcf8e3c52476
|
|
various regression tests for the issues that prompted its inclusion all now
pass in its absence
Change-Id: Ia375322335b4272aa6c3d626b2d98bc64465bf1c
|
|
and make the list (by its makefile proxy) a dependency of the output
so that removing an entry will trigger a rebuild of the target and
incremental builds are possible
Change-Id: I18c8d5ea2140e61b2ef78e256871402be94b79e2
|
|
Change-Id: Ic45b89d5cc1238bb58a29ed0e5fe967e23caefd5
|
|
Change-Id: I6194d6649983e1be075e39ac106b87e4a235b105
|
|
Change-Id: I6648adb99f2d67d24951d72b9fc13628d42dec51
|
|
Change-Id: I2c4d752677eeaa210242f37a54ecd20cb5703bb7
|
|
|
|
I can see no reason to have specific catalan rules, old examples
work fine with default rules
Change-Id: Ifacb7b46204d8aed543ab0c77fe80d1d5c5de738
|
|
Change-Id: I5b457531fb94f66dd7f5fdcc4636c5a202a036f1
|
|
Change-Id: I7785746b2cf4e5e054ced5b728dc69e6b1a966f2
|
|
Change-Id: Ie47dfe6ab5e308c0353d557fe7530a983622db96
|
|
Change-Id: I8d75eeb2eee43e1338a6f54c4b8ed633631bac0d
|
|
Change-Id: Ifad0a8ae01386db80a5eca9dfba8ee6841980139
|
|
Change-Id: Ia53fcbde6b3ff4d38b477069a1f956c9aef84f78
|
|
Change-Id: I97a554169637740aab4282b303a32f476f294e2f
|
|
Change-Id: I06f4578f6d681064a8e41e4bef45a7034b7b5a64
|
|
Change-Id: I589cedcd2db0208b03d1e28babbb493912f20c78
|
|
a) the default properties for the code point make it not split a word it
appears in into two different words in any break mode we have. Which is what we
want from a CH_TXTATR_INWORD
b) unicode TR#20 gives for the interlinear annotation anchor: "What to do if
detected: In a proxy context or browser context, remove U+FFF9", so when we
need to strip it from text to run that text through e.g. the spellchecker or
word counting then there's a solid precedent for stripping it
In addition I *do* want the footnote placeholder to break the word it appears
in, that gives the desired wordcount and cursor travelling behaviour
The BREAKWORD and other *random* selection of CH_TXTATR are still odd choices,
and there's way too many of them.
Change-Id: I930ff8ff806af448829bc1a1ae6cb92053e9a284
|
|
Change-Id: Ia34c2f18cfa84447578604ff27a9145d17bf354a
|
|
Change-Id: If2cb8da2a24331cc01fed85750747fff3d2fc8e0
|
|
a) remove special handling of 0x0002 in our custom icu rules.
Which brings us a step closer to getting rid of at least
some of them in favour of the defaults
b) expand the 0x02 in SwTxtNode::BuildConversionMap like we
do for fields so
Good side effect is our word count and character count now take into account
the actual footnote indicator text, as does our cursor travelling. Both of
which are more word-alike.
Change-Id: I3b0024ac4b10934bee7a9e83b0fce08a18556c7b
|