Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


That's not what I meant. I realise I can change the locale settings but my problem is that there is a minor problem with the locale settings. I've set the right locale (gd) but the comma shouldn't be there and I'm trying to figure where in the chain the error occurred (i.e. in the translation process, the minimal xml dataset, the large dataset off CLDR) because that affects the best way of putting it right.

Michael

29/10/2011 20:25, sgrìobh Cor Nouws:
Hi Michael,

Michael Bauer wrote (29-10-11 15:17)
Quick question - if the date format in LO is showing up as
31, December 2011
but it should be
31 December 2011

Is that a setting in LO that I messed up or did I mess up the locale xml?

Tools > Options > Language settings > Language allows to choose the locale.
That influences the default for new documents.
This can be changed ..
In Writer, the language of the text influences the representation of the date. In Calc, the language of the cell (Style) (number format) does the same.

HTH,



--
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


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.