Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[epf-dev] Re: EPF Content Call Tomorrow 
Folks,

I too have a conflict tomorrow and will not be available for our call.

Cheers,

Kim Werner

Sent from Windows Mobile PDA Phone
--- Begin Message ---
Title: epf-dev Digest, Vol 33, Issue 1

Send epf-dev mailing list submissions to
        epf-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        https://dev.eclipse.org/mailman/listinfo/epf-dev
or, via email, send a message with subject or body 'help' to
        epf-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
        epf-dev-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of epf-dev digest..."


Today's Topics:

   1. Auto internationalization for content names (Kristian Mandrup)
   2. Tomorrow's EPF status call (Chris Sibbald)
   3. How to translate in other languages  ? (Moreno, Mario)
   4. RE: Tomorrow's EPF status call (Oster, Nate)


----------------------------------------------------------------------

Message: 1
Date: Tue, 2 Sep 2008 11:24:51 +0200
From: Kristian Mandrup <kristian.mandrup@xxxxxxx>
Subject: [epf-dev] Auto internationalization for content names
To: epf-dev@xxxxxxxxxxx
Message-ID:
        <OF5CAC2E3C.C06E7859-ONC12574B8.0032E658-C12574B8.0033B6EB@xxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://dev.eclipse.org/mailman/private/epf-dev/attachments/20080902/19b66861/attachment.html

------------------------------

Message: 2
Date: Tue, 2 Sep 2008 10:46:33 -0400
From: Chris Sibbald <Chris.Sibbald@xxxxxxxxxx>
Subject: [epf-dev] Tomorrow's EPF status call
To: <epf-dev@xxxxxxxxxxx>
Message-ID:
        <OF37FCD302.CF762103-ON852574B8.0050FE8F-852574B8.00512E49@xxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

Hi Folks,

I have a conflict and will not be able to attend tomorrow's EPF status
call.

Cheers,
Chris

Chris Sibbald, Ph.D., P.Eng.
Senior Systems Engineer
Mobile: +1 (613) 266 - 5061
Fax: +1 (613) 739 - 4786
chris.sibbald@xxxxxxxxxx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://dev.eclipse.org/mailman/private/epf-dev/attachments/20080902/02f639fb/attachment.html

------------------------------

Message: 3
Date: Tue, 2 Sep 2008 17:04:32 +0200
From: "Moreno, Mario" <mario.moreno@xxxxxxxxxx>
Subject: [epf-dev] How to translate in other languages  ?
To: <epf-dev@xxxxxxxxxxx>
Message-ID:
        <C4F32BC268EF764BA625010C2BFD2CA72C08F1@xxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

Hi,



I'm looking for informations on how to produce a HTML site with EPFC
totally translated in other languages and how to deal with several
languages.

Many thanks for giving me some advice or pointers to documents on the
subject.

Thanks also to the community for providing such a nice tool and
methodological content.

Mario



This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://dev.eclipse.org/mailman/private/epf-dev/attachments/20080902/0c5b45af/attachment.html

------------------------------

Message: 4
Date: Tue, 2 Sep 2008 11:58:49 -0400
From: "Oster, Nate" <NOster@xxxxxxxxx>
Subject: RE: [epf-dev] Tomorrow's EPF status call
To: "Eclipse Process Framework Project Developers List"
        <epf-dev@xxxxxxxxxxx>
Message-ID:
        <7FC0856662DCB74091EB941CFA0B4487061528B7@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

Ken Clyne and I are teaching an Agile Workshop tomorrow and won't be
available during the call.



Thanks,
Nate



________________________________

From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Chris Sibbald
Sent: Tuesday, September 02, 2008 10:47 AM
To: epf-dev@xxxxxxxxxxx
Subject: [epf-dev] Tomorrow's EPF status call




Hi Folks,

I have a conflict and will not be able to attend tomorrow's EPF status
call.

Cheers,
Chris

Chris Sibbald, Ph.D., P.Eng.
Senior Systems Engineer
Mobile: +1 (613) 266 - 5061
Fax: +1 (613) 739 - 4786
chris.sibbald@xxxxxxxxxx

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://dev.eclipse.org/mailman/private/epf-dev/attachments/20080902/3ee7fc2f/attachment.html

------------------------------

_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev


End of epf-dev Digest, Vol 33, Issue 1
**************************************

No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.169 / Virus Database: 270.6.14/1646 - Release Date: 9/1/2008 6:03 PM


--- End Message ---

Back to the top