I'm not sure that there is any reason that this:
could not be coded like:
"gml_ID_alias" "Number" ##### must be i18n
"gml_NAME_alias" "Name" ##### must be i18n
could not be coded like:
"gml_ID_alias_en_US" "Number" ##### must be i18n
"gml_NAME_alias_en_US" "Name" ##### must be i18n
"gml_ID_alias_fr" "...." ##### must be i18n
"gml_NAME_alias_fr" "...." ##### must be i18n
"gml_ID_alias_es" "...." ##### must be i18n
"gml_NAME_alias_es" "...." ##### must be i18n
if someone wanted to make a change to mapserver to support it. I hate
the idea of having multiple mapfiles for the same map. It is a huge cost
to build and maintain and test them if you have to make changes or
update them.
-Steve W
On 10/7/2010 4:06 AM, teeschke wrote:
Hi Michael,
thats a realy good idea for the attributes of the geodata. But what about
LAYER
NAME 'my_highway_layer'
TYPE LINE
DATA "geom from data where lang='%lang%'"
METADATA
"ows_title" "highways" ##### must be i18n
"ows_group_title" "Infrastructure" ##### must be i18n
"wms_feature_info_mime_type" "text/html"
"wms_server_version" "1.1.1"
"wms_format" "image/png"
"wms_exceptions_format" "application/vnd.ogc.se_xml"
"gml_featureid" "ID"
"gml_include_items" "ID,NAME"
"gml_ID_alias" "Number" ##### must be i18n
"gml_NAME_alias" "Name" ##### must be i18n
END #METADATA
CLASS
NAME 'good' ##### must be i18n
COLOR 0 255 0
END # CLASS
CLASS
NAME 'bad' ##### must be i18n
COLOR 255 0 0
END #CLASS
END # LAYER
I think the only solution is to provide one mapfile for each language.
Thanks a lot and regards,
Daniel
_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users
