I don't have a lot of experience here, but I know that the group who is
doing a lot of this and using JSPs puts tokens in the JSPs and has a token
replacement file in each language. Makes it easier for translators not to
wade through HTML. I think the actual substitution is done at runtime.
Think beyond the technology and about how those translations and raw views
are managed over time and by what type of resource.
On a related note, often times, the content changes are managed by a
different group and part of a separate build process. So, being able to
package the templates and translations separately from the component code
is pretty critical.
-C
----- Forwarded by Christian Hall/Technology/Equifax on 09/10/2002 03:18 PM
-----
|--------+---------------------------------------------->
| | [EMAIL PROTECTED] |
| | Sent by: |
| | [EMAIL PROTECTED]|
| | eforge.net |
| | |
| | |
| | 09/10/2002 03:12 PM |
| | |
|--------+---------------------------------------------->
>-------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED] (Tapestry Developer)
|
| cc:
|
| Subject: [Tapestry-developer] Tapestry and L10N
|
|
|
>-------------------------------------------------------------------------------------------------|
I want to open the discussion about localization in
Tapestry.
I've gotten a steady trickle of feedback from beyond
western europe where they are using Tapestry, and it
isn't all good.
The stuff Tapestry does well, such as localizing assets
and providing access to localized string properties, is
perfectly ok.
The problem is that when you get beyond latin-1 charset,
things aren't as good. There's so much going on ...
browsers, fonts, UTF-8, HTML, HTML entities ... it's
hard to figure out what's going wrong.
I just tried an experiment, opening the response stream
as "text/html; charset=UTF-8" and got mixed results
(some characters in the french and italian render as
boxes rather than characters). I have no idea what I'd
get if I was using a Chinese or Japanese character set.
So ... who out there has the expertise to identify whats
right and what's wrong in Tapestry's localization?
--
[EMAIL PROTECTED]
http://tapestry.sf.net
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
Protect yourself against identity theft with Equifax Credit Watch. Visit
http://www.creditalert.equifax.com.
This message contains information from Equifax Inc. which may be
confidential and privileged. If you are not an intended recipient, please
refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have
received this transmission in error, please notify by e-mail
[EMAIL PROTECTED]
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
