Hello Kristian. That is one of the reasons why EPFC has two names. We do not recommend using non-ASCII character for the name to avoid such problems. The presentation name is the name that can use full UTF characters. However, many web servers actually support serving urls with utf characters. It mostly is a web server configuration problem to avoid the resource not found error.
Thanks and best regards, Peter Haumer. ______________________________________________________________ PETER HAUMER, Dr. rer. nat. Rational Method Composer | Eclipse Process Framework Rational Software | IBM Software Group Tel.: +1 (408) 463-5096 ______________________________________________________________ From: Kristian Mandrup <[EMAIL PROTECTED]> To: [email protected] Date: 09/02/2008 02:25 Subject: [epf-dev] Auto internationalization for content names I am developing an EPF content model for a danish company. I frequently have names with special characters such as å, ø and å. This is allowed within EPF composer but when I publish a site I get a ressource not found error as these characters are encoded in the URL references but the resulting html files are not URL encoded. Thus I end up with a html file such as : Miljoevariable på udvikler PC_90A3AA5.html And an error when browsing the published site: The requested resource (/SOAudviklingsproces/TrygVesta_SOA_udviklingsmodel/guidances/supportingmaterials/Miljoevariable%20p%C3%A5%20udvikler%20PC_90A3AA5.html) is not available. I think EPF composer should give a warning on such invalid names or even better, auto encode/translate. For danish characters this would result in these auto translations: å = aa, æ = ae, ø = oe. Possible, the translation strategy could be configures from a properties file or using the Eclipse Preferences store . Kristian _______________________________________________ epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________ epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev
