Age | Commit message (Collapse) | Author | Files | Lines |
|
(cherry picked from commit 1eed4c837828c00dff4ef0b2cf29b1e2962e912d)
Change-Id: I36d74fe1555bd436f93a5fa595e7da05bbd37493
Signed-off-by: Michael Meeks <michael.meeks@suse.com>
|
|
Conflicts:
svl/AllLangResTarget_svl.mk
svl/Library_fsstorage.mk
svl/Library_passwordcontainer.mk
Signed-off-by: Luboš Luňák <l.lunak@suse.cz>
|
|
Yields measurable speedup on load/store of large documents, wonder where
the equivalent patch i committed long time ago to OOo went...
Signed-off-by: Bjoern Michaelsen <bjoern.michaelsen@canonical.com>
|
|
|
|
|
|
* SvNumberFormatter::IsNumberFormat() ISO 8601 date input results in
yyyy-mm-dd format if no other date format was set.
* SvNumberFormatter::GetInputLineString() preserves ISO 8601 date format for
editing if such was set.
|
|
The slideshow uses the UNO API to access the drawing objects,
so add a property to get the temp file URL from the media object.
(cherry picked from commit 5924454a867bd500fdc696bb9939c84425c5e025)
|
|
|
|
|
|
|
|
|
|
|
|
Once smaller than 1582-10-15 decrementing a Date will not produce a valid date.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A compile time check ensures the common case of streaming just a plain
C-style string literal still produces reasonably compact call-site code.
The format-string variants are still available in sal/detail/log.h, but
only to be used in obsolete osl/diagnose.h etc., and going to be removed
again eventually.
|
|
|
|
|
|
* Locale data:
* nominative (nouns) month names always given in <MonthsOfYear>
element
* optional genitive case month names in <GenitiveMonths> element,
following the <MonthsOfYear> element; if not given take nominative
names
* optional partitive case month names in <PartitiveMonths> element,
following the <GenitiveMonths> element, or following the
<MonthsOfYear> element if the <GenitiveMonths> element is not
present; if not given take genitive case names, or nominative if
genitive names aren't defined
* currently known partitive case matters in Finnish locales
* Rules for use of nominative / genitive / partitive case month names in
number formatter:
* no day of month (D or DD) present in format code => MMM or MMMM
display nominative month name (noun)
* day of month (D or DD) after MMM or MMMM => genitive name
* no genitive names defined => nominative names
* day of month (D or DD) before MMM or MMMM => partitive name
* no partitive names defined => genitive names
* no genitive names defined => nominative names
|
|
* New SAL_INFO..., SAL_WARN... macros.
* New SAL_STREAM supersedes OSL_FORMAT.
* oustringostreaminserter.hxx moved from unotest to rtl (and always UTF-8 now).
* TODO to enable GCC __attribute__((format)) in sal/log.h (requires call-site
cleanup).
* Further functionality in tools/debug.hxx (DBG_MEMTEST, DBG_CTOR, etc.) not yet
addressed.
* Some replacements tools String -> rtl::OUString.
|
|
|
|
While introducing Calendar2 and the XCalendar3 interface anyway, as well the
"one letter" narrow month names sometimes needed in calendaring can be added.
These are not always the first capitalized letters of the months in all
locales, and might even not necessarily be just one character.
Introduces a new struct css::i18n::Calendar2 that is not derived from
css::i18n::Calendar because it uses a new struct css::i18n::CalendarItem2 to
hold the NarrowName elements.
In locale data the elements DaysOfMonth, MonthsOfYear and GenitiveMonths now
have an optional element DefaultNarrowName. If not specified, the first
character of DefaultFullName is taken.
LocaleDataWrapper and CalendarWrapper use and return the new Calendar2 and
sequences of CalendarItem2 structs. Application code adapted.
The number formatter now displays narrow month names (genitive if applicable)
for the MMMMM code, previously it displayed the first 16 bit code point of the
full name (not even utf-16 aware).
Narrow day names currently are not used, except in svtools' Calendar control.
|
|
* Switching between noun and genitive case month names is very simply done:
* If the format contains a day of month (D or DD) code, genitive case is used.
* If there is no day of month, the month noun is used. For example for
a standalone MMMM code or a combined MMMM-YYYY code.
* For input both, noun and genitive case, forms are recognized.
|
|
|
|
|