Hi :)
True. The reason i suggested an Extension is because
1. someone said they already had some C# coding to do at least part of this
2. i think it's faster than getting something into the main branch and dealing with all the
politics and systems of another group (ie the devs group)
3. Once something is tested as an Extension it seems that it's a lot easier to pull it into the
main branch
We do need more programmers/devs and doing an Extension might help someone work their way into that
group. I think the devs are quite a welcoming bunch and have things such as "Easy Hacks" and a
mentoring system to help people learn how to code for LibreOffice (and in general too). We already
have a lot of programmers but there is always room for more.
We are usually mostly short of people in the documentation group and it's documentation that is
usually the problem with most OpenSource products but by sheer coincidence quite a few new people
have just recently joined so we can look forward to guides for the 3.4.x branch arriving within the
next few weeks.
Guides for the 3.3.x branch are at
http://wiki.documentfoundation.org/Documentation/Publications
along with 3rd party documentation. The French team have an excellent FAQ which a couple of people
are trying to translate into English although that is where we are really short of people.
Regards from
Tom :)
--- On Thu, 1/12/11, Bruce Carlson <bruce@grahamgroup.com.au> wrote:
From: Bruce Carlson <bruce@grahamgroup.com.au>
Subject: RE: [libreoffice-users] French/English date
To: users@global.libreoffice.org
Date: Thursday, 1 December, 2011, 11:31
Hi,
In reply to Julius.
I understand your explanation and it seems to me that what you are asking for is a permanent
correction or addition to an existing function in the French localisation and I'd imagine that that
would not be too difficult to do. Although I have no real idea of how the current formats are coded
but I appreciate the frustration people using the French localisations must feel.
However your original post on this subject has sparked much interest and has led to other possible
adaptations of your original request such as:-
1. multi language ordinal functions. Imagine being able to select a range of cells in calc and
setting the format to "ordinal" for any number value.
2 . expanded functionality in creating custom number and date formats including the use of
ordinals to allow for people to create their own formats from local custom not only national
language.
3. and one I have introduced and that is being able to save custom formats with a friendly name
that can be, once saved, selected from the existing format list as and when required.
You may also be correct in these ideas not being solved by an extension but by actually modifying
the LO code itself, that is, embedded directly into LO may be a better solution.
However please don't think that these expansions of your original post detract in any way from the
importance of your original post because what you have brought to everyone's attention is the need
to correct an existing flaw, not to introduce a new function, although in order to do what you have
asked does require the creation of some new functions and it is these new functions that has
sparked everyone's imagination as to other possible uses .
Bruce Carlson
-----Original Message-----
From: julius.becker@gmail.com [mailto:julius.becker@gmail.com] On Behalf
Of Julius Becker
Sent: Thursday, 1 December 2011 9:23 PM
To: users@global.libreoffice.org
Subject: Re: [libreoffice-users] French/English date
Hi at all,
creating an extension might be a solution, but in my opinion, it isn't a good
one.
In French dates like "1er d cembre 2011", the ordinal number for the first day
of a month isn't an option, it's obligatory. You cannot say
"1 d cembre 2011" like LO does. So, LO should offer the possibility for ordinal
numbers without a special extension.
The same for English dates. In classes of students who learn English as a
foreign language, it would be very useful to have a long form of the English
date on worksheets, including "st", "nd", "rd" and "th".
Doug is right that one could simply _write_ and copy the date, but in my
opinion, "fields" are there to ease the work.
Since "DDDDD" could mean in French 1er, 2, 3, 4, 5, 6, ..., it could be
introduced even for English as 1st, 2nd, 3rd, 4th, 5th, 6th, ...
Kind regards,
Julius
--
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
--
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.