Bug 150991 - Ordinals in date field format do not save in writer
Summary: Ordinals in date field format do not save in writer
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.1.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Fields
  Show dependency treegraph
 
Reported: 2022-09-16 12:47 UTC by Ian
Modified: 2023-09-15 03:06 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian 2022-09-16 12:47:56 UTC
Inserting a date field in writer with a format that includes ordinals works as intended however when the document is saved (format tested ODT) and reloaded, the ordinals are no longer present either in the displayed date or format.

This bug was not found in Calc. Calc 7.4.1 was tested by formatting a cell containing 16/9/2022 to the format shown below. It worked as expected. Saving (as ods), closing and reloading showed the format was maintained as expected.

Date format used:
[NatNum12 D=ordinal-number]D" day of "MMMM YYYY

In Writer this was saved as ODT. Closed and reloaded. Date has lost it's ordinal.

For example:
Insert->Field->date
"Additional format"->as above under "Date format used:"

Date shown is "16th day of September 2022" (as expected).

Editing the field (double clicking) shows the format as "16th day of September 2022"

Saving the file as test.odt, closing file and reopening. The date is now shown as "16 day of September 2022" missing the "th" ordinal.

Editing the field (double clicking) shows the format as "16 day of September 2022" also missing the ordinal

Tested on non-fixed date in Writer 7.4.1 running on Ubuntu 22.04.1 AMD64 on 16 September 2022
Comment 1 Dieter 2022-09-30 06:48:41 UTC
Can't confirm with

Version: 7.4.1.2 (x64) / LibreOffice Community
Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

Perhaps only Linux?
Comment 2 Buovjaga 2023-02-15 14:10:40 UTC
I can't reproduce on Linux with 7.4 or latest unstable.

Do you still see this?

Arch Linux 64-bit, X11
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9ee1b714c13db308c199172ffa0199405ca3d9c3
CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 14 February 2023
Comment 3 QA Administrators 2023-08-15 03:15:18 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2023-09-15 03:06:17 UTC
Dear Ian,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp