https://bugs.documentfoundation.org/show_bug.cgi?id=159533
Heiko Tietze <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://ask.libreoffice.org | |/t/separator-after-custom-n | |umber-range-without-heading | |-number/101549/3 --- Comment #11 from Heiko Tietze <[email protected]> --- (In reply to William Friedman from comment #10) > Fields | Variables | Number Range | Format And how do you cross-reference this field? > Is there any reason not to file an enhancement request to fix them? You are getting me onboard - but still no cigar :-) Seriously, you define a use case that needs to be solved, not a solution that we have to implement. UX should verify the use case, ensure it's generic, without impact on other workflows, and eventually suggesting the UI/UX part of implementation. Technically we are limited by the format. ODF 1.2 defines 7.4.13 <text:sequence> The <text:sequence> element has the following attributes: style:num-format 19.500 style:num-format The values of the style:num-format attribute are 1, i, I, a value of type string 18.2, an empty string, a or A. 19.503 style:num-suffix The style:num-prefix and style:num-suffix attributes specify what to display before and after the number. I read this as if we can access the style:num-format in a text:sequence but not the style:num-suffix. It requires a change to the file format (that needs to be implemented in all applications - and all other formats too). -- You are receiving this mail because: You are the assignee for the bug.
