On 7/20/07, pat <[EMAIL PROTECTED]> wrote: > Johan, > > ...a note; I just 'plonked' Exhibit into an LAMP-server and ran the > JSON-file with (President) Håkan Röde of Håkanstenen, buried at Hovgården, > Adelsö, Mälaren. Not a very successful attempt -- especially with 'Adelsö' > and 'Mälaren' processed as list-facets.
Okay. My best guess is you ran into encoding issues, all likely solvable using the good resources you listed as suggested reading. I am ubnable to help without a URL demonstrating your lack of success with this setup. > > > Until a tagged API 2.0, I'll just keep-off polling the old 'onji'/'moji' > > > then. > > > > Um, I think we may have lost one another now. I tried to say there should > > be no known i18n issues with >neither 1.0 nor 2.0, but that 1.0 had working > > localization too, as an added bonus. > > Oh, I'm just jesting; 'onji' and 'moji' are the phonetic- and character- > symbolsets of japanese -- two of those, (2) that is, in the same language. Ah. (I would have recognized them under names like hiragana/katakana/kana and kanji.) > --> Do take a look at http://www.joelonsoftware.com/articles/Unicode.html. I > especially like the part about "What do web browsers do if they don't find > any Content-Type, either in the http headers or the meta tag?". Which was why I suggested you to take explicit action to pick a well defined content type to avoid the whole problem class. Be unmistakably clear about what you emit, and browsers will not fail to heed your command. Exhibit can't help you to get things right, unless your data is delivered web standards compliantly. > >> Now, I final thought, I wonder how the Javascript API escapes [pun] > >> the recently added non-ASCII URL's. No respone needed -- I'm just > >> saying... :) > > > > Is your problem that you are failing to load data files from urls like > > http://räksmörgås.nu/? > > -> Yep, that's what I'm talking about; [...] In that case, your issues are not in Exhibit land, but in web standards and browser object model land. Exhibit will treat as URLs what a browser understands as a URL, and if you name your sites and files in a way that will not be found on your web server when requested, neither will Exhibit. You can debug this by placing an image on your web server under the name you try to load your JSON files from, but with some extension that will give it an image content type (.jpg, for instance), and link to that file using an <img> tag. If it loads, you're fine. If it doesn't, debug the problem and try options until you get it to work. Then apply the same solution to loading your exhibit data file(s). > > As mentioned, we'd be able to help you debug your issues if you gave an > > example URL to the exhibit you are having problems with (or one exhibiting > > the same issues, if the data is private). > > -> I'll 'whip-something-together', in time, and we'll see. Sounds good. -- / Johan Sundström, http://ecmanaut.blogspot.com/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
