On 7/19/07, pat <[EMAIL PROTECTED]> wrote:
> Hi, I really don't want to be a 16th-century conundrum about a '19th-century
> ditto'...
>
> But, 'twiddling' with Exhibit, I once again had to battle the lacking
> support of nordic letters in the solutions available. Bringing me to the
> following questions:
>
> 1. Is any work started at Simile regarding internationalization?
Yes; the 1.0 API even has some Swedish localization, if your browser
is set to ask for that first, in fact. For the 2.0 API under
development, localization needs some more reworking, but will likely
happen before the release.
Regarding the pure internationalization issues, you should not be
affected by anything that web development in general isn't also
affected by, so if you keep your content types correct (my tip: go
with a content-type of text/javascript;charset=UTF-8 for your json
files, and ascertain that the data is UTF-8 encoded, if you can, and
otherwise opt for ISO-8859-1 or ISO-8859-15 otherwise) and mark up
your data appropriately, things should basically just work.
> 2. Has anybody programmatically solved the issue of having to use either
> 'HTML &'- and/or 'UNIX \'- escapes in the Exhibit JSON-datafiles, hoping to
> by-pass the lacking 'non ASCII'-support?
That works too, but is much less elegant. \u00E5 equals å in
javascript strings. Use proper JSON to be sure, i e {
"s\u00E5":"h\00E4r" }, not { s\u00E5:"h\00E4r" }, to be sure. (I'm not
sure s\u00E5 is a legal javascript identifier, even though Firefox
seems to accept it.)
If you encode your exhibit data as HTML tables, you can use whatever
HTML escaping methods you prefer, or plain using the native
representation as per the page's content type. An example:
http://exhibit.ecmanaut.googlepages.com/choir-events.html#basic
> 3. Unwilling to reinvent anything available or rather load the project into
> Eclipse and step-debug the code; anyone with an idea about where the
> JSON-data is read into the Exhibit-code, thus enabling an intercept and
> letter replacement -- say, replacing the letter 'å ' with '\u00E5' -- before
> end-user presentation?
I think you're better off giving us a link to an exhibit whose
non-ASCII letters become garbled; your error is likely elsewhere.
> Per memoria: The issue above might not be seen as a serious problem to
> ASCII-based users
There are people on the dev team that are not native speakers of
ASCII; don't worry. :-)
> Finally, I assumed that the further idea with AJAX/JSON was to simplify
> polling information from other sources than the webserver. As the above
> exemplifies, it's very hard to do so in Exhibit.
I'm doing just fine with my hacks at
http://exhibit.ecmanaut.googlepages.com/ (many of which are probably
running with the under-development 2.0 branch) but I'll grant you that
there could probably be much better docs about things and potential
pitfalls in the Exhibit wiki. I'd very much welcome you to improve
those, when you've found the source of your problem.
--
/ Johan Sundström, http://ecmanaut.blogspot.com/
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
