Changes

Jump to navigation Jump to search
m
added Luxembourg to the list of countries which have bilingual products
Line 8: Line 8:  
** Bilingual products
 
** Bilingual products
 
*** Products where all the texts on the label are in two (or more) languages
 
*** Products where all the texts on the label are in two (or more) languages
*** Common in bilingual countries (Belgium, Canada...)
+
*** Common in bilingual countries (Belgium, Canada, Luxembourg, ...)
 
*** e.g. most Cora products have all the text in French and in Dutch: http://world.openfoodfacts.org/brand/cora
 
*** e.g. most Cora products have all the text in French and in Dutch: http://world.openfoodfacts.org/brand/cora
 
* Products with some information in multiple languages
 
* Products with some information in multiple languages
Line 47: Line 47:  
** Only if the category exists in the taxonomy
 
** Only if the category exists in the taxonomy
 
** Only if the target language exists for this category in the taxonomy
 
** Only if the target language exists for this category in the taxonomy
*** If the target language doesn't exist, English is used to display the field value
+
*** If the target language doesn't exist, English is used to display the field value (or the entry language? --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 17:21, 15 November 2015 (CET))
   −
* Nutrition facts are displayed in the target language
+
* Nutrition facts are displayed in the target language (if available in the taxonomy --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 17:23, 15 November 2015 (CET))
** The nutrition facts are displayed according to the country (different order and presentation for EU nutrition tables vs US/CA nutrition tables)
+
** The nutrition facts are displayed according to the country (different order and presentation for EU nutrition tables vs US/CA nutrition tables). This is set by the system. The user can not specify which table format is on the label. (I bought a product with a US label in a french shop --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 17:26, 15 November 2015 (CET))
   −
* Fields without a taxonomy are displayed in the language they were entered in
+
* Fields without a taxonomy are displayed in the language (the main language) they were entered in
** common name, quantity, packaging, brands, origin of ingredients, manufacturing or processing places, city/state/country, stores, link to the product page, best before date
+
** common name, quantity, packaging, brands, origin of ingredients, manufacturing or processing places, city/state/country, stores, link to the product page, best before date (shouldn't there be a common formatting attempt for fractions and dates, dependent on the main language? --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 17:29, 15 November 2015 (CET))
 
** ingredients  
 
** ingredients  
   −
* Images for product front, ingredients and nutrition facts are for the main language of the product (and not the target language)
+
* Images for product front, ingredients and nutrition facts are for the main language of the product (and not the target language). (These images are the same as the ones at data entry, i.e. no special processing for display has been applied --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 17:34, 15 November 2015 (CET))
 
      
== Solution ==
 
== Solution ==
Line 65: Line 64:  
* Taxonomize as many fields as possible
 
* Taxonomize as many fields as possible
 
** Taxonomized field need to be completed in only one language
 
** Taxonomized field need to be completed in only one language
** Packaging, origins of ingredients, purchase places
+
** Packaging, origins of ingredients, purchase places, (shops --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 17:40, 15 November 2015 (CET))
 
*** Note: packaging and purchase places do not correspond to text on the label
 
*** Note: packaging and purchase places do not correspond to text on the label
    
* Enable users to enter data for more than one language:
 
* Enable users to enter data for more than one language:
** Select different images or different part of the images for product front, ingredients and nutrition facts
+
** Select different images or different part of the images for product front, ingredients and nutrition facts (Usually multi-lingual nutrition facts are found in the same table, but undoubtedly exceptions exist. But do no require multiple image selections when it not necessary --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 17:55, 15 November 2015 (CET))
 
** Enter data (text) for more than one language
 
** Enter data (text) for more than one language
 +
** Allow users to use another language than the main language through the use of a prefix 'nl:' for example. This is useful for country specific labels, c.f. '[http://world-fr.openfoodfacts.org/cgi/search.pl?search_terms=Glasbak&search_simple=1&action=process Glasbak]', 'Ecoponto azul', etc. --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 17:55, 15 November 2015 (CET)
    
* We keep the "main language" field
 
* We keep the "main language" field
** Indicates the most prominent language on the label
+
** Indicates the most prominent language on the label (and thus the data entry language used. Not sure whether 'the most prominent' should be a requirement. If I buy a prominent arabic/english product in Egypt, I will only be able to enter the eglish part of the label --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 17:55, 15 November 2015 (CET))
 
** When the split is 50% / 50% (e.g. some products sold in Belgium with one side in Dutch and another side in French), picking either is fine.
 
** When the split is 50% / 50% (e.g. some products sold in Belgium with one side in Dutch and another side in French), picking either is fine.
    
=== Data display ===
 
=== Data display ===
   −
* Taxonomized fields will be displayed in the target language
+
* Taxonomized fields will be displayed in the target language. (What about country specific labels? Target language (and thus translation) is nice, but the corresponding label should be displayed as well. It helps a non-native speaker to interpret the labels --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 18:00, 15 November 2015 (CET))
* Display other fields and pictures in the target language if the product has data in that language
+
* Display other fields and pictures in the target language if the product has data in that language. (No translation!? --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 18:00, 15 November 2015 (CET))
* Indicate in which languages the product data is available, and provide a way to see it
+
* Indicate in which languages the product data is available, and provide a way to see each language
 
      
=== Interface design ===
 
=== Interface design ===
    
* How to make data entry not too overwhelming?
 
* How to make data entry not too overwhelming?
* Solution 1: tabs to switch between languages
+
* Interface should take into account touch interfaces (touch targets large enough) --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 18:57, 15 November 2015 (CET).
 +
* Not all language dependent fields need to be present on a label, so do not multiply all fields for all languages --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 18:57, 15 November 2015 (CET)
 +
* Solution 1: tabs to switch between languages (slide-down menu? One tab per product or one tab per relevant field? --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 18:04, 15 November 2015 (CET))
 
** + button to add a language tab
 
** + button to add a language tab
 
** tab displays only the fields that need to be completed in other languages:
 
** tab displays only the fields that need to be completed in other languages:
 
*** images
 
*** images
*** fiels like generic name, ingredients
+
*** fields like generic name, ingredients
 
* Solution 2: multiply each field by the number of languages, display all languages for one field together
 
* Solution 2: multiply each field by the number of languages, display all languages for one field together
 
** + button to dynamically add a new language
 
** + button to dynamically add a new language
Line 98: Line 99:  
==== Taxonomize all or most multilingual tag fields ====
 
==== Taxonomize all or most multilingual tag fields ====
   −
* Packaging, origins of ingredients and purchase places are tag fields (they contain comma separated values) that are not yet taxonomized
+
* Packaging, origins of ingredients and purchase places are tag fields (they contain comma separated values) that are not yet taxonomized. (Origin of ingredients is a two part tag: ingredient+origin. How to keep them apart? --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 19:05, 15 November 2015 (CET))
* The existing taxonomy system will take care of the mapping between different languages
+
* The existing taxonomy system will take care of the mapping between different languages (country and language specific labels? --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 19:05, 15 November 2015 (CET))
 
* The taxonomies need to be created or completed
 
* The taxonomies need to be created or completed
 
* To be determined: what to do with brands?
 
* To be determined: what to do with brands?
Line 105: Line 106:  
*** But exceptions exist
 
*** But exceptions exist
 
** Could benefit from being taxonomized in order to have a hierarchy
 
** Could benefit from being taxonomized in order to have a hierarchy
 
+
** An Hierarchy could also help to normalize brands, i.e. remove errors --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 19:05, 15 November 2015 (CET)
    
==== Selection/crop of images in more than one language ====
 
==== Selection/crop of images in more than one language ====
Line 120: Line 121:  
* Create new fields suffixed by _lang, with a hash
 
* Create new fields suffixed by _lang, with a hash
 
** "ingredients_text_lang":{"en":"Chocolate, milk", "fr":"Chocolat, lait"}
 
** "ingredients_text_lang":{"en":"Chocolate, milk", "fr":"Chocolat, lait"}
 +
** So multiple languages can be found in the same field. --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 19:18, 15 November 2015 (CET)
 
* Create new languages field
 
* Create new languages field
 
** Hash that contains languages for which we have values for at least one field
 
** Hash that contains languages for which we have values for at least one field
 
** "languages":{"en":"1", "fr":"1"}
 
** "languages":{"en":"1", "fr":"1"}
 +
** What is the purpose of this field? --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 19:18, 15 November 2015 (CET)
 +
Could there be conflicts between the ingredients_text qnd ingredients_text_lang fields? And how should these be resolved?
 +
Could the number of hashes in *_lang fields be different? Also different in content (i.e. "it" and "en" in one field and "fr" and "nl" in another field)
 +
--[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 19:18, 15 November 2015 (CET)
1

edit

Navigation menu