Hi, Dmitry. I've done some digging. "us-ascii' was selected for portability, ease of inspection/editing, and ease of processing by non-UTF-8-capable tools. There are no plans to change the encoding for the OpenJDK website. iris -----Original Message----- From: Dmitry Samersoff Sent: Thursday, November 15, 2012 11:35 PM To: Iris Clark Cc: Tuva Palm; svc-internal_ww_grp; Oleg Pekhovskiy; Shanliang Jiang; Jean-Francois Denise; Gerard Ziemski; guide-discuss@openjdk.java.net Subject: Re: FW: Developers' Guide: 0.02 Iris, Thank you for clarification. I'm not familiar with doc process, so please forgive my ignorance. One think makes me worried - when I switch from translated (utf-8) to not translated (us-ascii) page it requires browser to switch encoding. Browsers doesn't do it correct always, especially on mobile devices. So I would prefer to use the same, utf-8 encoding, across all docs if it possible. -Dmitry On 2012-11-16 07:16, Iris Clark wrote:
Hi, Dmitry.
The source for the guide specifies encoding="iso-8859-1". The XSL stylesheet for openjdk.java.net specifies "us-ascii" so that's what the majority[1] of the entire site's .html uses, regardless of what's specified.
iris
[1]: JavaDoc .html files aren't processed.
-----Original Message----- From: Dmitry Samersoff Sent: Thursday, November 15, 2012 1:17 PM To: Tuva Palm Cc: svc-internal_ww_grp; Oleg Pekhovskiy; Shanliang Jiang; Jean-Francois Denise; Gerard Ziemski; guide-discuss@openjdk.java.net; Iris Clark Subject: Re: FW: Developers' Guide: 0.02
Iris,
What is the reason of using us-ascii but not utf-8 ?
-Dmitry
On 2012-11-15 14:09, Tuva Palm wrote:
FYI?
*From: *Iris Clark <iris.clark@oracle.com <mailto:iris.clark@oracle.com>>
*Subject: Developers' Guide: 0.02*
*Date: *November 7, 2012 6:24:29 PM PST
*To: *guide-discuss@openjdk.java.net <mailto:guide-discuss@openjdk.java.net>
Hi!
Just thought I'd let you know that I just pushed an update to the Guide [1] (webrev [2]). Don't get too excited, all I did was a quick pass to remove the obviously incorrect (e.g. s/Sun/Oracle/g), eliminate references to plans that never materialized or things that longer exist, run it through the W3C Markup Validator, and bump the version number/date.
There's still additional work that could be done. There's no grand plan here. It just made me sad to see the Guide languishing for attention.
Thanks,
iris
-- Dmitry Samersoff Oracle Java development team, Saint Petersburg, Russia * Give Rabbit time, and he'll always get the answer
-- Dmitry Samersoff Oracle Java development team, Saint Petersburg, Russia * Give Rabbit time, and he'll always get the answer