Just saw this email now. Good feedback Kristian. One goal of EPFC is to provide one look at feel for all published pages. We therefore discourage setting fonts etc. in individual elements. There are actually css and xsl files in the installation directory that you can adjust to make such changes. Rational Method Composer externalizes all these files (the same one) into Skins that you can easily swap out against each other.
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/04/2008 04:07 Subject: [epf-dev] RE: Re: Auto internationalization for content names (Peter Haumer) Hi Peter, Thanks for your reply. Yes, I realized that I should use the Presentation names for the non-ascii characters, but I just thought it was odd that EPF allows non-ascii names at all. Myabe it could just provide some kind of warning (yellow icon?) or allow one to configure a naming policy in the preferences? When I manage the processes, and edit the Work breakdown structure, I end up with the same presentation and identifier names when creating a new Task Descriptor fx, but when I edit such a name (in the tree structure), only the presentation name is updated. Not totally obvious IMO and leads to the same problems. I think in general that EPF should enable some settings in the preferences. Would also be nice to configure the standard Font to be used. I used a lot of Word documents we had as initial source (Times New Roman, 3) but when I edit within EPF Rich Editor my font is switched to Arial,2 when writing a new paragraph etc. Would be nice to allow default font to be set individually for each Content element, overriding the default font for the entire plugin. Just some ideas... The cleanup could also be configured/customized by using a XSLT to transform the XHTML from Tidy to the XHTML required to better keep in line with individual layout policies. Keep up the good work! :) Kristian --- Message: 1 Date: Tue, 2 Sep 2008 23:40:34 -0700 From: Peter Haumer <[EMAIL PROTECTED]> Subject: Re: [epf-dev] Auto internationalization for content names To: Eclipse Process Framework Project Developers List <[email protected]> Cc: [email protected], [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" 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. Possibly, 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
