Formatting numbers in Writer table to comma separated reverts to non-comma separated

Hi all,
I recently discovered that Number Format (among other types of format) can be applied on numeric data in a cell in LibreOffice Writer table. And I am thrilled.
So I started using it extensively, where ever within the document the need for it arose.
I am referring to, for example, I can convert a number like 12345 to be more readable by applying comma separation format, to 12,345, which is really neat.
However, after exiting from LibreOffice Writer and re-opening the document, the numbers revert to 12345, i.e. the comma separation is no longer retained. Re-applying the same ‘comma separation’ does not work.
Is there a way to bring back the number with ‘comma separation’ I applied to earlier?
Thanks in advance.

OS name, LO version and save format? The latter is very important because ODF standard (the native format for LO documents) contains features not implemented in DOCX (and vice versa). So, number format could be one of them.

To make sure, attach a sample file of yours.

2 Likes

LO-docx-number-format.docx (11.7 KB)

Here you go, OS name, LO version and save format, and an abridged sample file saved in .docx format. The original file is much larger of course, and contains many table with such math done at the bottom of each table.

  • OS name: MS Windows, version 23H2 (OS Build 22631.4460)
  • LO version: 24.8.2.1 (X86_64) / LibreOffice Community
  • Save format: Word 2007 (*.docx)

docx

Here you go, using an external file format, not capable of holding the feature that LibreOffice Writer has (but not MS Word).

1 Like

Elaborating on previous comment

In brief

To reliably use all the functionality native to LibreOffice (LO), you need to save your document in the native LO file format (odt).

The “full story”

If you need to collaborate, and perhaps even co-edit, with people who must use MS Word, there will be problems of this kind. In such situations, at best agree on one application/suite for all collaborators to use. Otherwise, focus on creating content, and make design (formats, layout) the last step of a project.

Note that Word is also able to open odt files. However, the issues caused by transitioning between MS and LO contexts are not likely to improve much from such a change.

If you receive mandatory Word-format templates or you are required to submit your work in Word file format, the only way around the issue is to acquire a Word license and do the work in Word, assuming that a similar solution exists there. (I believe that there is, but on sick leave atm so no MS install at hand to check with.)

MS Office and LO will mostly work fine in a side-by-side install on your computer. You need to pay some attention to default file type assignments, and avoid repeated transitions between MS and LO contexts for your files. With each such transition, translation residue/loss will build up.

1 Like

@ajlittoz , @keme1 , @mikekaganski

I am sorry to learn you are on sick leave at the moment, and wish you get well very soon @keme1! Moreover, an MS Office install at hand is not needed.

Now the Number Format works like a charm though - after changing the file format native to LO. Thank you both for pointing this out.

Being new to LO and coming from a background of having used MS Word mostly, and not knowing .odt, I presumed .docx would be the choice external file format to pick. I see now, this is not the case.

I agree to your elaborate review in the full story and agree to using one application/suite for all collaborations, and, to focus on content and design to be the last step of a project. This, is the key!

AT the moment, I am not required to utilize or submit work in Word file format, nor do I have the need to.

I am discovering LO and I work along. It’s a treasure!

Pay special attention to the fact that if you converted your document from DOCX to ODF, it is already “polluted” by the mixed edit history. If you want to have a reliable and stable document from now on, I highly recommend you create a new blank document into which you paste as unformatted text the present contents. You’ll have to re-style everything but this will prove beneficial instead of being subjected to already present “approximations” and bad conversions.

1 Like

I’ll make a note of the @ajlittoz .

Yes, I switched from DOCX to ODT. I have the data saved in individual calc files. What I did now is I inserted linked OLE objects to fill the tables in the writer document rather than pasting unformatted data.

Re-styling.
Yes, I have come across this issue. I had to reapply font size and face - despite having it preset for table contents.