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


Hi :)
Each time a new branch starts a whole load of people stick with the previous branch.  

The initial x.x.0 and x.x.1 have had tons of new features and things added but the flip side of 
that is that they are less reliable.  Who wants stable and reliable tho, right?  Surely everyone 
seeks the shiny new toys and glamorous new looks?  Well, quite a lot of people do put more value on 
stability and reliability than on being fancy and flash.  Some of us don't even try a branch until 
it has settled into the x.x.4 or more which is around when the unexpected flaws seem to have been 
ironed out.  

Both these links help search through the bug-tracking thing and help post bug-reports
http://wiki.documentfoundation.org/BugReport
https://www.libreoffice.org/get-help/bug/

Regards from
Tom :)  


--- On Wed, 29/8/12, Mirosław Zalewski <miniopl@poczta.onet.pl> wrote:

From: Mirosław Zalewski <miniopl@poczta.onet.pl>
Subject: Re: [libreoffice-users] Ver. 3.6.1 still bad recognition date.
To: users@global.libreoffice.org
Date: Wednesday, 29 August, 2012, 23:07

On 29/08/2012 at 22:50, Rafał Piszczek <sklep@optiland.pl> wrote:

Up to ver. 3.5.6 when I wrote "23/8" or just "23 /" changed to 23.08.2012 -
now despite cell format as a date - nothing changes ... For me it falls
off. Daily I have to write on a sheet about 150 dates. So I am forced to
stay with version 3.5.6.

This mailing list is intended to provide user support by other users. We are 
not developers and I am unsure what do you want us to do with this.

Anyway:
can you find your issue on bug-tracking system [0]? If so, then check if you 
can provide any additional information.
If no, then please send bug report. You can then send us link to your report 
here and ask us to confirm it (I can already confirm).

Also, please read these two blog posts [1] [2]. In second one you will find 
information how to provide additional patterns. Before proceeding with them, 
you may want to get in touch with Polish localization team - either ask at LO 
l10n mailing list [3], or Polish support forum [4] (you are from Poland, 
right?).

If you need help with translating messages to English (and you are indeed from 
Poland), then feel free to send me message off the list - I will try to help 
you there.

[0] http://goo.gl/6MnBO
[1] http://erack.org/blog/archives/8-LibreOffice-date-acceptance-patterns.html
[2] http://erack.org/blog/archives/archives/18-Does-your-LibreOffice-locale-
need-a-date-acceptance-pattern-for-incomplete-date-input.html
[3] https://www.libreoffice.org/get-help/mailing-lists/
[4] http://user.services.openoffice.org/pl/forum/
-- 
Best regards
Mirosław Zalewski

-- 
For unsubscribe instructions e-mail to: users+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/users/
All messages sent to this list will be publicly archived and cannot be deleted

-- 
For unsubscribe instructions e-mail to: users+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/users/
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.