Bug 52048 - FORMATTING: Support user-defined identifier sequences (numbering) for ordered lists (refer comment 4)
Summary: FORMATTING: Support user-defined identifier sequences (numbering) for ordered...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
: 52348 103335 (view as bug list)
Depends on:
Blocks: Numbering-Formats
  Show dependency treegraph
 
Reported: 2012-07-13 11:56 UTC by Kevin Hunter
Modified: 2022-05-31 11:36 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
Writer custom outline (147.15 KB, image/png)
2015-05-25 22:31 UTC, Koika
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Hunter 2012-07-13 11:56:53 UTC
Problem description: 

Feature request: Add an option in Outline Numbering to use spelled out versions of numbers.

Certain manual and professional document formats use text numbers in outline formats, rather than digits.  Usually it's in book, part, and chapter headers, and sometimes in section headers.

Example, if I have a document structure like this:

- Chapter 1 A Title
-- Section
...
- Chapter 2 Another Title
- Chapter 3 Yet Another Title

Then the format I'm talking about might look like:

Chapter One: A Title
Chapter Two: Another Title
Chapter Three: Yet Another Title.

i.e. use of 'One' over the numeral '1'



Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04 Chromium/18.0.1025.168 Chrome/18.0.1025.168 Safari/535.19
Comment 1 A (Andy) 2012-12-25 18:09:47 UTC
I agree, this would be a nice feature.  
The BULLETS AND NUMBERING function could have some improvements (see e.g. also Bug 57337).
Comment 2 A (Andy) 2012-12-25 18:35:10 UTC
*** Bug 52348 has been marked as a duplicate of this bug. ***
Comment 3 Emanuele Gissi 2014-09-25 07:10:30 UTC
*** Bug 55436 has been marked as a duplicate of this bug. ***
Comment 4 Emanuele Gissi 2014-09-25 07:22:13 UTC
This issue and all the linked duplicates could be solved by adding the possibility to specify "custom numbering formats".

I imagine a "Custom" entry in the "Numbering" popup menu found in several dialogs:
- Tools > Outline numbering > Numbering
- Format > Bullets and numbering > Options

If the user selects that entry, an additional edit field near to the popup menu should get enabled, into which the user can enter the list of ordered desired symbols, separated by blanks and/or commas, like any of these:
- first,second,third,fourth
- primo,secondo,terzo,quarto
- x,xx,xxx
- *, †, ‡, £
or as in my case:
- "Generalità","RTO","RTV","Metodi"

Thank you very much for your effort!
Here is what we are currently doing with LibreOffice:
https://code.google.com/p/italian-fire-code/
Comment 5 Eyal Rozenberg 2014-09-25 07:30:29 UTC
(In reply to comment #4)
So, perhaps rename this bug to reflect the 'folding' of the duplicates into it? e.g. "Allow for custom numbering sequences"?

Also, one can think of specifying sequences manually (i.e. giving, for each number up to something not-so-small, a string value), but the more relevant method should be programmatic, i.e. some function of the form

string getNumberRepresentation(unsigned integer number)
Comment 6 Owen Genat (retired) 2014-09-27 12:22:20 UTC
Summary amended for clarity. Related Ask thread: http://ask.libreoffice.org/en/question/40211/
Comment 7 Emanuele Gissi 2014-09-30 09:39:36 UTC
How to push for a quick solution?
Can I propose a bounty?
Emanuele
Comment 8 Kevin Hunter 2014-10-24 13:30:49 UTC
(In reply to Emanuele Gissi from comment #7)
> How to push for a quick solution?
> Can I propose a bounty?

Honestly?  Find a developer and pay them fair wages.  How you do this is up to you, and a bounty is good option.  However, you might have better luck soliciting the services of a small development/consulting shop in your area -- folks with whom you can talk face-to-face.  (Note that you might want to require as part of your contract with said shop that they discuss their change on the LibO development mailing list and must have their patch-set accepted into master, etc.)

The biggest item lacking in much open source development is money, so if you are motivated by this (or any problem) and have available funds, you can move this process along.  I'd certainly appreciate your efforts if you went this route.
Comment 9 Eyal Rozenberg 2014-10-24 14:06:56 UTC
(In reply to Kevin Hunter from comment #8)
> Honestly?  Find a developer and pay them fair wages.  

Kevin, that's not a fair comment, as almost all users of LibO (or any other FOSS I guess) do not have the kind of money available to sponsor a software developer.

Maybe if the ODF had some sort of 'donation-for-feature'/bounty bins, end-users could pool money into them - but not individually.
Comment 10 Kevin Hunter 2014-10-24 18:26:25 UTC
(In reply to Eyal Rozenberg from comment #9)
> (In reply to Kevin Hunter from comment #8)
> > Honestly?  Find a developer and pay them fair wages.  
> 
> Kevin, that's not a fair comment, as almost all users of LibO (or any other
> FOSS I guess) do not have the kind of money available to sponsor a software
> developer.

Apologies; was not meant to offend.  I thought the intent of his question was "how to get moving on this getting this enhancement in?"  And the answer to that is either "wait and hope that a core developer has time/inclination to do it", or "encourage a new (non-core) developer to do it."  In regards to open-source software, those are basically the only two options.  The bounty option he suggested is a version of "pay them fair wages".

Put differently, I don't expect him to personally fund a developer; I, like most other LibO users, am in the exact boat you describe (no feasible opportunity to sponsor a software developer).  But he asked "how to push for a quick solution", which I answered.

> Maybe if the ODF had some sort of 'donation-for-feature'/bounty bins,
> end-users could pool money into them - but not individually.

It doesn't have to be individually, nor do I think I suggested that.  Again, I answered his question as asked.  If you've a better suggestion or answer, please do share it.  If I misunderstood, and he was asking for bounty communities, I can google as well as you.  For example:

    https://freedomsponsors.org/

    https://www.bountysource.com/search?query=libreoffice

But your not wrong that it is perhaps a missed opportunity that TDF doesn't have their own version.
Comment 11 Koika 2015-05-25 22:31:21 UTC
Created attachment 116034 [details]
Writer custom outline
Comment 12 Koika 2015-05-25 22:41:30 UTC
More than 10 spots should also be defineable. Chinese use there version of romans numerals to track things. It is a 10x12 systems. Ten Heavenly stems, 甲[jia3],乙[yi3],丙[bing3],丁[ding1],戊[wu4],己[ji3],庚[geng1],辛[xin1],壬[ren2],癸[gui3],as the first level and twelve earthly stems as the second level
子[zi3],丑[chou3],寅[yin2],卯[mao3],辰[chen2],巳[si4],午[wu3],未[wei4],申[shen1],酉[you3],戌[xu1],亥[hai4]. 

The image is taken under Fedora 21. Noticed there are less buttons on the bottom than.

Note the Show at Sublevel: doesn't seem to do anything, nor does the Start at:, when entering custom entries.
Comment 13 Koika 2015-05-25 22:42:27 UTC Comment hidden (obsolete)
Comment 14 Timur 2016-02-22 18:27:19 UTC
Just to note that MSO up to 2016 doesn't have user-defined numbering like this, but it has common ones: One, Two...; First, Second...; 1st, 2nd...
Comment 15 Stanislav Horacek 2016-10-20 21:30:53 UTC
*** Bug 103335 has been marked as a duplicate of this bug. ***
Comment 16 Regina Henschel 2017-04-05 21:47:15 UTC
Greek numbering is discussed in https://issues.oasis-open.org/browse/OFFICE-1426
Comment 17 László Németh 2022-05-31 11:36:33 UTC
(In reply to Emanuele Gissi from comment #7)
> How to push for a quick solution?

@Emanuele: See modifying Numbertext's Soros programs, which are plain text files in a LibrEOffice installation to set arbitrary custom lists (only on your machine):

https://bugs.documentfoundation.org/show_bug.cgi?id=145239#c11