points as decimal separator instead of commas, and no thousands separator in layout composer

[stadtentwicklung]

Describe the bug

How to Reproduce

QGIS and OS versions

Additional context

[stadtentwicklung]

Attribute table (1) uses commas as the decimal marker, which is correct. But the layout (2) uses different notation, with points for decimal separators and no thousands seperator. The settings seems right (3).

[stadtentwicklung]

Here is the root Information:
https://gis.stackexchange.com/questions/346999/the-shape-table-in-qgis-layout-shows-no-decimal-points

[roya0045]

Update your qgis and please report if this is still the case.

[stadtentwicklung]

okay I'll do …
and by the way the QGIS opening window fits perfect in the default vlc player window...

[stadtentwicklung]

as @roya0045 said, I updated QGIS from 3.4.7 to 3.4.15. The problem is still existing. See the screenshot. Issue again: points as decimal separator instead of commas, and no thousands separator in QGIS 3.4.15 layout composer (but in the "map-canvas" everything is fine -> see attachement please).

[elpaso]

This was never implemented.

I could work on it, but I'm not sure if @nyalldawson has plans.

Additionally, something that we might want to add is to optionally add the language information to the layout, so that when opened on QGIS instance with a different language setting (think about the server context where we want prints with a certain language configuration).

[stadtentwicklung]

So if I understand you right, the language information of content in the layout-composer is a individual one, free and independent? All Information after your third comma I do not understand.

[elpaso]

So if I understand you right, the language information of content in the layout-composer is a individual one, free and independent?

It was never implemented: there is no locale support in layout composer tables.

All Information after your third comma I do not understand.

Sorry for not being clear, what I meant is that when (and if) it will be implemented, we will need to keep in mind that we might want to allow a different behavior than the most part of QGIS: instead of always getting locale information form user profile settings, we might want to be able to override the locale settings for the print layouts individually, just in case your project contains different layouts for different locales.

[stadtentwicklung]

Thank you for your answer. I still not understand. The setting is in the canvas perfect and works fine with decimal commas and thousand separators. I assume, that the canvas setting shows the locale setting. This locale setting is not consider by the composer. The composer setting is not clear in my opinion. It should get the "locale canvas setting" too.

[elpaso]

Thank you for your answer. I still not understand. The setting is in the canvas perfect and works fine with decimal commas and thousand separators. I assume, that the canvas setting shows the locale setting. This locale setting is not consider by the composer. The composer setting is not clear in my opinion. It should get the "locale canvas setting" too.

I agree. But the piece of code that does that was never written: it was never implemented, so technically it's not a bug.

[stadtentwicklung]

Okay chrystal clear. How can I go on?

[elpaso]

The usual way, you have a few options:

• fix it yourself if you can
• wait and hope that someone fixes it for you
• launch a crowdfunding campaign to get it financed
• contact a QGIS core developer and fund the development

[stadtentwicklung]

The checkbox "System-Locale überschreiben (override)" is not activated (top of the pic). (But) All numbers are beautiful in the attribute table (the end of the pic). The default of "System-Locale" has access to the right settings. What are these settings? Is it a lot of work to implement that default setting in the composer? Where can I start?

[stadtentwicklung]

[stadtentwicklung]

Sorry my answer was not clear. I would try to fix it by myself and I was asking for an entry point. I decide to start with the GitHub repositories.

[gioman]

If the issue is valid/confirmed it must stay open.

[elpaso]

@gioman if this is a bug or a feature request is debatable.
I think it's a bug, but it was never implemented in the first place.

IIRC @nyalldawson has been made aware of that and he had plans, but we spoke about that a long time ago, so I may be mistaken.

The fix can be trivial or complex depending how we decide to handle it (see my comments above regarding the server situation).

[gioman]

@gioman if this is a bug or a feature request is debatable.
I think it's a bug, but it was never implemented in the first place.

sure, but one or the other does not matter, if the bug/request is a valid one.

[github-actions]

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.