4,561
edits
Changes
Jump to navigation
Jump to search
Line 40:
Line 40: − + + + +
Open Food Facts API Version 2 (view source)
Revision as of 16:06, 28 October 2020
, 16:06, 28 October 2020→Multilingual support
It is also possible to limit the product languages provided. eg. only products with main language dutch, or products that have dutch. This falls either under the category search or filtering.
It is also possible to limit the product languages provided. eg. only products with main language dutch, or products that have dutch. This falls either under the category search or filtering.
A related question is how languages should be encoded in a resulting json.
A related question is how languages should be encoded in a resulting json. For each language dependent field the corresponding language must be known. There are three options:
# Adapt field names - add a postfix to a field name to indicate the language, i.e. name_fr. Draw back of this approach is that the relevant postfixes are not known before hand. A list of possible languages in the json circumvents this. However this requires more extensive programming for the api user. (This approach is currently used).
# Simple dictionary - encode a language dependent fields as a dictionary, i.e { "en":"in english", "fr":"en français"}. This keeps the drawback that the fieldnames are not known before hand;
# Structured dictionary - any field that can be in a specific language can be encoded as a standard "language" dictionary: { {"languageCode":"en", "languageValue":"in english"}, {"languageCode":"fr", "languageValue":"en français"}
= Product read API =
= Product read API =