Schema.org wrong price

[gregzawadzki]

Theme uses following code to show prices on product page for Google etc.

<meta itemprop="price" content="{$productPrice}">

However, this might create price like:
<meta itemprop="price" content="939.332"> (real price is 939.33)

Google thinks its thousand separator not decimal separator and on listings shows enormous amount of 939.332,00 in this case.

Fix:
<meta itemprop="price" content="{$productPrice|round:2}">

To apply in product.tpl and product-wide.tpl

[cienislaw]

what about 3 decimal places currencies?

[gregzawadzki]

It's my quick-fix for my store. It's not a solution. Maybe there should be even no solution and its not a bug.

It's rather to adapt to Google than to official standard.

Solution would be to use decimals defined per currency. However, that would also require testing how google interprets it?
Also how it works in 3 decimal currencies?

TL;DR

According to schema org . (a dot) is prefered decimal places separator. Google does not see it like it and (wrongly) interprets it as thousand separator.
According to schema.org it's good without rounding. Adapting to google would require.

This problem happens to PLN. And as you probably know. For Polish , is decimal separator and \`` or [space]` is thousand separator.

Long version

Basically... according to schema.org/price:

• Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similar Unicode symbols.
• Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.

So according to specs that's good as it is now. Without "rounding".
But and Google does not seem to honor it. It tries to be smarter.

It all depends if we do it for Google or for specification it seems.
However, specs do not declare how many decimal places are allowed...
So, who is schema.org for? Should we adapt to google interpreting it wrongly?

Best solution would be to fix google... but let's be honest... i don't think it's ever gonna happen unless they feel like it.

The most real solution (i think should work) is to use rounding from currency. And let's hope Google will work good for 3 decimal currencies.

[cienislaw]

don't get me wrong - I'm aware that Niara and thirtybees itself is full of 'issues' and some of them can not be easily fixed or user base affected by it is very small. thats why I'm logging them on github to rise awareness.

as You mentioned the best solution is to get decimals count from currency itself. it can be 0, 2 (most popular) and 3 (7 of them). decimal separator accepted by google is another thing to have in mind.

[gregzawadzki]

Nah. I know you try to note about currencies. I did not think of it and good you pointed it out :)
Just wanted to note this can be rather complicated if google has "very specific understanding of numbers"