Page: http://wiki.cocoondev.org/Wiki.jsp?page=LenyaI18N , version: 105 on Sat 
Dec 27 21:09:31 2003 by RolfKulemann

- __Documents can be authored and served in multiple languages.__ Each language 
version is stored in a separate file fitting a file name pattern which 
currently is myfilename_locale.xml i.e. tutorial_de.xml or tutorial_en.xml. The 
''language negotiation protocol'' is simply defined within the request url. 
Should mean, a Lenya class i.e. the DefaultDocumentBuilder searches for a 
language identifier like _en or _de in the request uri. Based on that 
information the appropiate language version of the requested document is 
served. If you request i.e. tutorial_de.html all links in that page point to 
_de.html versions assuming that a german version of the destination exists. 
Request to uris without a language identifier are routed to a document version 
in the publication's default language.
+ __Documents can be authored and served in multiple languages.__ Each language 
version is stored in a separate file fitting a file name pattern which 
currently is myfilename_locale.xml i.e. tutorial_de.xml or tutorial_en.xml. The 
''language negotiation protocol'' is simply defined within the request url. 
Should mean, a Lenya class i.e. the DefaultDocumentBuilder searches for a 
language identifier like _en or _de in the request uri. Based on that 
information the appropiate language version of the requested document is 
served. If you request i.e. tutorial_de.html all links in that page point to 
_de.html versions assuming that a german version of the destination exists. 
Request to uris without a language identifier are ''always'' being routed to a 
document version in the publication's default language.
?                                                                               
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
       +++++++++++++++++



Reply via email to