Version 11 (modified by 13 years ago) ( diff ) | ,
---|
google summer of code 2011 - inspire view service support
tasks
multi language support
A language specific metadata values "wms_title" "my title" "wms_title" "mein titel" | B language dependent reference data DATA "shapes/rivers_eng.shp" DATA "shapes/rivers_ger.shp" | ||
1 key extension | "wms_title_eng" "my title" "wms_title_ger" "mein titel" | --- | main question: should resolution happen at i) write time, i.e. only wms_title goes into mapobject or ii) read time, i.e. everything goes into mapobject, corresponding key e.g. wms_title_ger is used for reading mapfile maintainable? validation? |
2 runtime substitution | --- | DATA "shapes/rivers_%language%.shp" with language being a request parameter or global setting | already implemented in mapserver for certain parameters all required substitution scenarios (parameters) covered? |
3 externalization using external files lang.eng lang.ger | "wms_title" "IDC_TITLE" IDC_TITLE=my title IDC_TITLE=mein titel | DATA "IDC_SHAPES_RIVERS" IDC_SHAPES_RIVERS=shapes/rivers_eng.shp IDC_SHAPES_RIVERS=shapes/rivers_ger.shp or IDC_SHAPES_RIVERS=shapes/eng/rivers.shp IDC_SHAPES_RIVERS=shapes/ger/rivers.shp | common way of internationalization, many tools available to externalize strings at which time the externalized value should be resolved (while parsing mapfile, during msApplySubstitutions, ...)? |
...
status reports
Note:
See TracWiki
for help on using the wiki.