We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some ingredients are wrongly parsed to specific ingredients in PL language
Example product: https://world.openfoodfacts.org/product/4056489019091/fruit-to-go-freshona Aslo: https://world.openfoodfacts.org/api/v2/product/4056489019091
Those ingredients are NOT specific ingredients but there are ingredients.
jabłka and zagęszczony sok z aceroli are parsed as ingredients. whereas all others are parsed as specific ingredients.
I first thought that it is because those ingredients may not be recognized. But no, because for example "przecier z mango" is recognized as mango with processing "pureed". It seems to be language related because if we google translate the list of ingredients in EN, it works fine: https://world.openfoodfacts.org/cgi/test_ingredients_analysis.pl?ingredients_text=84%25+[…]ted+acerola+juice.&type=add&action=process&submit=Envoyer
I suspect that it could be related to the function "parse_specific_ingredients_from_text" that we reworked recently with Stephane. But not sure.
The text was updated successfully, but these errors were encountered:
You can also see it in products with ingredients list in German https://world.openfoodfacts.org/product/4056489067726/vegan-spread-mexican-style-vemondo
Sorry, something went wrong.
benbenben2
Successfully merging a pull request may close this issue.
What
Some ingredients are wrongly parsed to specific ingredients in PL language
Steps to reproduce the behavior
Example product: https://world.openfoodfacts.org/product/4056489019091/fruit-to-go-freshona
Aslo: https://world.openfoodfacts.org/api/v2/product/4056489019091
Expected behavior
Those ingredients are NOT specific ingredients but there are ingredients.
Additional context
jabłka and zagęszczony sok z aceroli are parsed as ingredients.
whereas all others are parsed as specific ingredients.
I first thought that it is because those ingredients may not be recognized. But no, because for example "przecier z mango" is recognized as mango with processing "pureed".
It seems to be language related because if we google translate the list of ingredients in EN, it works fine: https://world.openfoodfacts.org/cgi/test_ingredients_analysis.pl?ingredients_text=84%25+[…]ted+acerola+juice.&type=add&action=process&submit=Envoyer
I suspect that it could be related to the function "parse_specific_ingredients_from_text" that we reworked recently with Stephane. But not sure.
The text was updated successfully, but these errors were encountered: