[0.77.3] Has there been a change in the number format in PP?

Hello,

As shown in the screenshot below:

When exporting to a CSV file, the numbers have a different format, either right-aligned, which is OK, or left-aligned, which causes all your calculations to return a #VALUE error.

Until now, I had no problems, but since yesterday, my entire calculation mechanism no longer works because of this.

I should mention that I use the following settings to perform the export.

Thank you for your help.

dregnier

Translated with DeepL.com (free version)

1 Like

I don’t know if this touched the export too.

1 Like

Obviously yes, and I can see from your contribution where the problem lies.

As can be seen in the screenshot, all the numbers in thousands are aligned to the left… for the simple reason that they have a space to separate the thousands.

I am appealing for help in finding out how to restore the previous situation. :woozy_face:

Thank you.

dregnier

I am searching but cannot find where I can download the previous version, the one from 22 June. Do you have a link you can send me?

Thank you

dregnier

I reverted to version 0.77.2 from 22 June, but the CSV export is still not functioning properly … :enraged_face:


Is this picture from libreoffice? Try German (Germany)

1 Like

The test in German does not change anything…

What is curious is that I went back to version 0.77.2 and I cannot find the proper functioning that was in place until then… ???

You will notice in the screenshot that the column on the left also has percentages aligned to the left. For those, I have a trick that consists of retrieving the cell in LibreOffice and multiplying it by 1, which aligns the percentage to the right.

This also worked for values, but this time it no longer does… I am a little disappointed :roll_eyes:

A workaround:
Select everything except the header row.
Then use the search/replace function in Calc (similar to Excel).
Search for: enter a space
Replace: enter nothig, leave it empy.

That should work, but try it on a copy of your file :slight_smile:
Stefan

It still works for me.
I think the main parameter to look into is your language within PP : did you change from Français_Canada to Français_France ?
I can open csv from PP from fr_ca settings in LibreOffice calc, but not from fr_fr

When I open csv from fr_ca, the grouping separator is NBSP : works with Libre Office
When I open csv from fr_fr, the grouping separator is NNBSP : does not work with Libre Office

I wonder if the “sanitize” that was done in 77.3 for copy paste values should also be applied to export, to remove those NNBPS.

2 Likes

Sorry for the impact. We’ll fix it.

With 0.77.3 the format how numbers are copied to the clipboard was slightly changed. Instead of the copying the string output as is, I am removing non-breaking invisible spaces - which made problems copying the cell content to Excel.

It looks to me that the importer now sees the space - instead of a non-breaking space - and interprets the whole “cell” as string. Hence the left alignment.

I have to wrap my head around this - I tested and Excel was not accepting the non-breaking spaces. But I did not test with Libreoffice which expects them. Maybe they behave differently. The local is fr_CA - need to check.

Maybe it is also different if “importing CSV” (= full lines, comma separated) from “pasting a cell” (= where different rules might apply to understand what is a number and what not)?!?

Update: The “fix” was removing the non-breaking spaces. But the screenshot shows spaces. Not sure I understand the root case already.

What confuses me a little that using 0.77.2 does not help. 0.77.2 just included the code to copy the cell content to the clipboard. But it did not manipulate that. It could be an indicator that theory above does is not right. Can you share what error message you get there?

There are two ways to create and export CSV:

If you do this from the File menu - bookings for cash and security accounts, securities - then I have the underlying model - strings, numbers - and create the CSV. I could also sanitize here (but let’s first understand the root cause). Actually, I wonder if the CSV should just not be internationalized - always English labels, always the same encoding, always the same formatting of numbers, always the same value separator (comma).

If you do this from a table, then I have the table strings as shown in the UX. I can extract the text from the table, but I do not necessarily know the underlying value. The value was a transient “thing” that by now is rendered and kept as string. It would be nice to have that separated - the calculated value from the formatted string - but that is not how the framework does it and how it is implemented. ~Therefore I do not know what is a number and I am - now - just stripping non-breaking spaces. This is where the sanitizing is applied (and creates the problem?!?)~

@Veterini You are right, the table exporter is not “sanitizing” anything. Only when copying to the clipboard.

@dregnier and share the locale of PP (in the settings - the screenshot that @Veterini shared)

I clearly don’t have the same level of knowledge about PP as you do. That’s a fact. What’s more, I’m French, and despite the translators, the language barrier makes it difficult to fully understand what is being said.

The screenshot from @Veterini caught my attention, and I reproduced his configuration as shown below:

And, once again, the CSV export works perfectly, and retrieval in LibreOffice no longer poses any problems:

However, all the percentages are still aligned to the left

Thank you for your help and for resolving my issue.
Is this feedback sufficient for you?

Best regards.

dregnier

P.S.: Small oversight, I am still using version 0.77.2 from 22 June 2025. I am going to upgrade to version 0.77.3, I hope it will still work…

I have just tested it with Libre Office.

I can confirm what @Veterini wrote:

  • When exporting with the fr_FR (French/France), then it contains NNBSP (narrow-non breaking spaces) that Libre Office cannot import
  • When exporting with the fr_CA (French/Canada), then it contains NBSP (non-breaking spaces) that Libre Office can import
  • If you select “Detect special numbers” during the import, the percentage are imported correctly.

This is how the sample looks like:

Which all does not explain why it “suddenly” stopped working for you. This code was not changed with 0.77.x releases.

Did you switch the locale? Some Update?

And, finally, I like the suggestion by @Veterini to also “sanitize” when exporting the full table to CSV. I change that with the version. That should make importing more stable.

In the meantime, you might want to select all rows, press Ctrl-C and paste it to LibreOffice. That includes no NBSP and NNBSP

Thank you @AndreasB for this additional information.

The percentages are OK and they are correctly aligned to the right.

I have no idea why this change has occurred. I haven’t changed location or updated my system.

However, I sometimes use a VPN that locates me abroad. Could this be related?