On Tue, Jul 20, 2010 at 2:24 AM, Pegasus Rider <[email protected]> wrote: > Regarding the URL part, I have to acknowledge that your decision is > basically right, with an exception of navigation for users whose > [native] script isn't Latin; I mean it breaks the default behaviour of > linking the available pages automatically, although the fix shall be > no more complicated than adding a character class ( [:alnum:] ) to the > allowed characters subset.
I certainly don't trust PoSix abominations like [:alnum:], really, any site that uses non-ascii characters in an URL is broken as far as I'm concerned. > Page titles are arbitrary UTF-8 strings indeed, they just appear prior > to character encoding declaration, which causes interpretation > problems (you may run W3C mark-up validator on a Werc-managed site > with non-ASCII title to check this out). Ah, interesting, now I see what you mean, I guess I had assumed the whole world had moved on to 'always-assume-utf-8' :) Thanks for pointing this out, I'll fix it. (Although I don't think the current arrangement breaks anything other than the w3c validator, and web browsers seem to handle it fine, but hey, it is trivial to fix, so...) uriel > Thanks for your help! > > -- > You received this message because you are subscribed to the Google Groups > "werc" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/werc9?hl=en. > > -- You received this message because you are subscribed to the Google Groups "werc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/werc9?hl=en.
