On Monday 21 November 2011, Eike Rathke wrote:
On Sunday, 2011-11-20 14:30:23 +0200, Harri Pitkänen wrote:
Has
anyone checked how this affects interoperability with Excel?
I think they use a similar approach for genitive case names (use them if
a day of month is present), but I haven't heard of partitive case.
It seems that things are a little bit complicated with Finnish Excel.
Essentially it does not have this feature directly in the date format
implementation but instead they have hardcoded the partitive suffix into those
predefined date formats that need it.
I tested this by creating a file in Excel and entering a date with different
formats. Then I saved it and opened the same file in LibreOffice 3.4.4. The
result can be seen in this screenshot:
http://www.puimula.org/htp/libreoffice/dformat.png
- The predefined format for the date containing partitive month names
translates to format string
[$-40B]P\. KKKK\t\a;@
(P is Finnish format character for day of month and KKKK is full month name.).
You can see that Excel hardcodes characters "ta" at the end of the month name.
This is visible when you open the file in LibreOffice but can also be seen
within Excel if choose the format and then go to custom format edit view.
There is no direct support for genitive month names in Finnish Excel (thus no
predefined formats where day of month precedes the month name), but of course
you can create the custom format yourself. So actually the current
implementation in Excel matches pretty much exactly LibreOffice 3.4.4 for
Finnish.
It seems to me that the intelligent month name format would lead to doubled
partitive suffixes when a document created in Excel is opened in LibreOffice.
We could avoid that by modifying the rule a bit: in case format specifier MMMM
(or KKKK in the Finnish example above) is immediately followed by a character
literal, nominative form is used even if there is day of month present in the
format. This would also avoid problems with older OpenDocument files where
people may have used similar hardcoded suffixes.
Even then users who take advantage of the new feature in LibreOffice will see
the month names incorrectly if they open the file in Excel. I don't see this
as a problem since no data is lost, the formatting problem is minor and it is
really just a missing feature in Excel which we cannot fix anyway.
Harri
--
Unsubscribe instructions: E-mail to l10n+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Re: [libreoffice-l10n] [ANNOUNCE] added possessive genitive case month names, HEADS UP localizers ; -) · Andrea Pescetti
Re: [libreoffice-l10n] [ANNOUNCE] added possessive genitive case month names, HEADS UP localizers ; -) · Valter Mura
Re: [libreoffice-l10n] [ANNOUNCE] added possessive genitive case month names, HEADS UP localizers ; -) · Eike Rathke
Re: [libreoffice-l10n] [ANNOUNCE] added possessive genitive case month names, HEADS UP localizers ;-) · Eike Rathke
Re: [libreoffice-l10n] [ANNOUNCE] added possessive genitive case month names, HEADS UP localizers ;-) · Kostas Mousafiris
(message not available)
added partitive case month names as well (was: [libreoffice-l10n] [ANNOUNCE] added possessive genitive case month names, HEADS UP localizers ;-)) · Eike Rathke
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.