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
... because otherwise types that have been removed from the input rdb
still end up in the resulting jar file.
Change-Id: Ia73ecffcc9d831f2627ac0fcc5f57acf1f52a799
http://srfi.schemers.org/srfi-13/mail-archive/msg00046.html summarizes well..
"
- Titlecase <> uppercase
Unicode defines three kinds of case mapping: lowercase, uppercase, and
titlecase. The difference between uppercasing and titlecasing a character
or character sequence can be seen in compound characters (that is,
a single character that represents a compount of two characters).
For example, in Unicode, character U+01F3 is LATIN SMALL LETTER DZ. (Let us
write this compound character using ASCII as "dz".) This character
uppercases to character U+01F1, LATIN CAPITAL LETTER DZ. (Which is
basically "DZ".) But it titlecases to to character U+01F2, LATIN CAPITAL
LETTER D WITH SMALL LETTER Z. (Which we can write "Dz".)
character uppercase titlecase
--------- --------- ---------
dz DZ Dz
"
See TestCharacterClassification::testTitleCase for titlecase regression
tests.
Change-Id: I198379832d1910632bb6358149a5276b68d7c6eb
There can be some serious rounding errors involved when calculating where to
draw the grid lines for the various row heights in a document. This can be
especially true for a document that has many different row heights.
This results in draw objects appearing to move relative to the grid line at
different zoom levels. This patch attempts to fix this problem adjusting
the position of the shapes as they are drawn to ensure their position
relative to grid appears to be stable. We do this by translating the position
of the shape to the corrosponding position of it's cell anchor. Of course not
all shapes are cell anchored and in this case we position the shape relative
a temporary synthesized cell anchor.
The patch essentially does the following
a) calculates the offset to be applied for each shape at the current zoom level
to ensure that the shape will be drawn relative to the correct cell grid
see drwlayer.cxx, drawview.cxx & gridwin3.cxx, svdobj.[ch]xx
b) apply the offset in the drawing layer for each of the different drawing
primitives see svx/source/sdr/contact/*
c) making sure the position and size of the newly created shape ( at any zoom
level ) are still as expected when zoom level is changed.
see. sc/source/ui/drawfunc/fuco*.cxx &
d) making sure that overlays and handles are displayed at the correct position
see svx/source/svdraw/*
it could also be that a full blown transform might be needed to additionally
scale the object ( to ensure that the edges of the object stay stable relative
to ajacent grid lines ) If necessary we could do that in a later step.
Change-Id: I02232f8ba192d58dbf96b80adf66c281cd0f65e8
String used to do some operation by modifying itself
whereas OUString never does that and when a modificaiton is needed
it create a new copy.
so it is very easy when one convert String code to OUString code to
miss stuff like
sString.ToUpperCase()
which need to be converted into
sString = sString.toAsciiUpperCase()
and not
sString.toAsciiUpperCase()
This patch make the compiler generate a warning in that later _wrong_ case
Change-Id: I4a9c0b4c7d0b75ad8850ac23b86e8508a334f5fe
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>
The OUString assignment operator is less transactional than it could be, but is
also not necessasry, as OUStringBuffer has a non-explicit conversion constructor
from OUString.
Added some missing @since tags.
Change-Id: I830be93fde78422c5a7eff9437b53e2d2d70933a
