Age | Commit message (Collapse) | Author |
|
Change-Id: I939160ae72fecbe3d4a60ce755730bd4c38497fb
Reviewed-on: https://gerrit.libreoffice.org/8182
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Change-Id: If67e1c48fba43fabcaffef92d96bc1377b4d1dd8
|
|
Change-Id: Id37ad55b8994b7ed40cdd569a016a68c7386b551
|
|
Namely: Estonian has several sets of correct quote mark glyphs for double
quotes („”, „“, «» are all common), however the Institute of Estonian
Language [1] recommends using the first of these, i.e. „” (99 low, 99
high) [2]. As for single quotes, Estonian texts rarely use them, except in
a few fields such as linguistics and biology -- and both ‘’ (9-9) and ’’
(6-9) are considered correct [2, 3]. However, apostrophe in the beginning
of a word (which is effectively the same as a starting single quote) can
also be used to indicate omitted character(s) -- but there, only ’ (9) is
correct [3].
[1] Eesti Keele Instituut, the main official body which maintains and
studies the usage of Estonian language; http://en.eki.ee/index.php
[2] The last page of
https://docs.google.com/viewer?url=http://keeleabi.eki.ee/pdf/164.pdf (in
Estonian)
[3] Handbook of Estonian Language,
http://www.eki.ee/books/ekk09/index.php?p=2&p1=11&id=86 (in Estonian)
Change-Id: If88e6e03e3e4aa1919a25dbe2fa2ffc8c9a04f4a
|
|
Change-Id: I7937b5ba09c00448678e71c1786f775998f0f6fa
|
|
Change-Id: I5011c4dfea02c8fab8ca3ee08bbed7f31396e3ec
|
|
Change-Id: Ib6dc7e409d89e4824b373db2cd7a13449c3c18ed
|
|
Change-Id: I0e1034a2ef064f9a3a05a0b8837efdff767ea715
|
|
Change-Id: Idfd95810f929d6485263c0a4fb1e24bfa31c48f8
|
|
Change-Id: I2a65485b8dcaa7b6ed4a049f97d460878b8bb17d
|
|
Change-Id: Ifd18bf16213a1c4b746eab16e563f0322fbc3690
|
|
Change-Id: I8c8e99036fe694a2fb0160250c7c0c4fefb98a3e
|
|
Change-Id: I64b038ad3b8d423dad6707fb0b2fd2127b2050a3
|
|
Change-Id: I018bbe39a30582f51cdd620b3bf3240456b7bd65
|
|
Change-Id: I5a0498a3871e2b90629af8ed6b725ff22f242fba
|
|
Change-Id: Id2346686ac2f6c537825d70cac1a537d09e351d5
|
|
Change-Id: I1d489cacaf4717ab395b22a92e6dd6645cb92b1c
|
|
3af99e4d59d89c343965a928681a30f36b1007d2 "convert equalsAsciiL calls to
startsWith calls" should rather have converted to oprator ==.
Change-Id: Id4a8836c5d6d570e54661c40be7214632e202b21
|
|
Change-Id: I5b372ce78268d16fc629a47228875d31a298e189
|
|
Change-Id: I674ee59803fa5a1987787cf98f369dee63729adf
|
|
Issue:
OUString uses UTF-16, so for a Unicode surrogate character there are 2
values stored, not just 1.
So we are getting assert failure in "rtl_uString_iterateCodePoints" method.
erAck: Underlying cause was that the dictionary breakiterator misused UTF-16 positions as Unicode code point positions.
Change-Id: I923485f56c2d879b63687adaea2b489a3479991c
Reviewed-on: https://gerrit.libreoffice.org/6955
Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>
|
|
Change-Id: I36dd015635c30f63e2085c250e159fbd536da611
|
|
Change-Id: Iee8da90c70589b8053c8c5b696afb4968072f47e
|
|
Change-Id: I9acc496cd95c8362972fa0c41d35b77fc0715aba
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>
|
|
...which it did unlike all the other implbaseN.hxx. Required lots of downstream clean-up,
of course.
Change-Id: Ib720e7a0a43410dcd7e6338b84a3973dfbb20866
|
|
Change-Id: I56f38bd786f3a026cb2908f28540dc9c4003af83
|
|
Change-Id: I823c112bca495eb8997f2dc098e712cd745759c5
|
|
It is no longer necessary to cast to sal_Unicode when calling
OUStringBuffer::append
Change-Id: Iab3d1e12eef472cfe11f1d0d1969ca404091dd7d
|
|
Convert code like
if( !aStr.isEmpty() && aStr[0] == 'x' )
to
if( aStr.startsWith("x") )
Change-Id: Iabc3a44ed3be2d29eed876e0eeef212ccd271edf
|
|
Except for our external api where the Oriya is stuck (and similar for
the vba implementation)
Change-Id: I8288c930567385eea49a4c303727b13ef8b8a89f
|
|
This breaks windows build with localized versions of MSVC.
Change-Id: I23c46830f96ae661eced88352476e7ae61fbcc2a
Reviewed-on: https://gerrit.libreoffice.org/6847
Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>
|
|
Change-Id: I73359a4e2c36ffeca71210971ba9be670e0a12ae
|
|
Change-Id: I390bfec0d36dcc9529785e97994dad2b0704dc80
|
|
A final pass through the code, converting code to use the new
OUString and OString methods that can detect string literals.
Change-Id: Ifa6382335e5650a1c67e52006b26354e0692c710
|
|
Change-Id: Ic31811c287e2dc2908243a228a340c3005077297
|
|
Change-Id: I59d553f7b70955de18562046f1d7aa5fae6e9fb1
|
|
Change-Id: I82b093f7778a9d85016903cad1e39fc97f696cf2
|
|
Convert code like:
aOStringBuf.append( RTL_CONSTASCII_STRINGPARAM( " is missing )") );
to:
aOStringBuf.append( " is missing )" );
which compiles down to the same code.
Change-Id: I3d8ed0cbf96a881686524a167412d5f303c06b71
|
|
Convert code like:
aStr.equalsAsciiL( RTL_CONSTASCII_STRINGPARAM( "ActiveConnection" ) )
to
aStr.startsWith( "ActiveConnection" )
which compiles down to the same machine code.
Change-Id: Id4b0c5e0f9afe716a468d3afc70374699848dc33
|
|
Complete set is now Y-M-D;M-D;M/D/Y;M/D
Change-Id: I42ed59fb325b391943608a10ded7ce74c80656e1
|
|
change code like
aStr = OUString("xxxx");
to
aStr = "xxxx";
Change-Id: Ib981a5cc735677ec5dba76ef9279a107d22e99d4
|
|
for AED and KWD currencies, simply referring [ar-SA] in all other
aspects
Change-Id: I2ca19d1f7d2e807406bf207babe76cae967eea81
|
|
Change-Id: I8069657d8829a0315c704e884a1cf15b26e02eb8
|
|
Change-Id: I56c1190c93333636981acf2dd271515170a8a904
|
|
Change-Id: Ibf04062ca86ed866202d748c3b62a210d30ed6ec
|
|
These horrible headers use "#pragma GCC system_header" and thereby
prevent generated Makefile dependencies, which is what broke incremental
builds after the ICU upgrade today.
Change-Id: Ife983b3c4de86968da8a0187a1acb1bbb2b5c81f
|
|
Change-Id: I6da721dc25394dfee12e3028aefbf0546d1be984
Reviewed-on: https://gerrit.libreoffice.org/6669
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
This reverts commit fc04b55f7f96a4f70f31c145dafd44c1d9276a41.
|
|
They are accessed from multiple threads frequently.
Change-Id: I3f9720ede076109efe0b7eaa4a05dd50f2e38102
|
|
Convert code like
aStr.compareToAscii("XXX") == 0
to
aStr.equalsAscii("XXX")
which is both easier to read and faster.
Change-Id: I448abf58f2fa0e7715dba53f8e8825ca0587c83f
|