Viktor wrote:
> James Bennett wrote:
>> Even when I copy/paste that URL (which I had to do, because my
>> web-based email client didn't recognize that the Cyrillic portion of
>> it was part of the URL) into Firefox, the URL encoding turns
>> "��_��" into
>> "%D0%93%D0%BB%D0%B0%D0%B2%D0%BD%
On 4/14/06, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote:
> I would sooner blame your setup or software for not properly
> supporting such links.
The thing is, this *is* "proper support". The URL is still accessed
correctly, and the page is displayed correctly. But the URL string
itsel
On 4/14/06, James Bennett <[EMAIL PROTECTED]> wrote:
> Which is a problem, because really the whole idea behind a URL slug is
> to provide some useful information about the page which lives at that
> URL. But a long string of URL-encoded characters doesn't convey any
> more useful information than
On 4/13/06, Viktor <[EMAIL PROTECTED]> wrote:
> We tested utf-8 urls against ie, opera and konqueror and they work
> great. Firefox by default shows the urls urlencoded, but you can change:
> network.standard-url.escape-utf8 to false
> and it will show the url in original encoding.
Using t
On Apr 13, 2006, at 10:34 PM, James Bennett wrote:
> Which is a problem, because really the whole idea behind a URL slug is
> to provide some useful information about the page which lives at that
> URL.
And if your users aren't speakers of languages that are normally
represented in ASCII text,
Ivan Sagalaev wrote:
> And in
> case of Firefox am I supposed to stick a big red banner on start page
> saying "To see this page properly in your browser go to
> about:config..."? :-)
>
as i understand, that's not required. firefox will correctly go to the
required url. it just will display i
James Bennett wrote:
> Even when I copy/paste that URL (which I had to do, because my
> web-based email client didn't recognize that the Cyrillic portion of
> it was part of the URL) into Firefox, the URL encoding turns
> "��_��" into
> "%D0%93%D0%BB%D0%B0%D0%B2%D0%BD%D0%B0_%D1%81%D1%82%D1
James Bennett wrote:
>Even when I copy/paste that URL (which I had to do, because my
>web-based email client didn't recognize that the Cyrillic portion of
>it was part of the URL) into Firefox, the URL encoding turns
>"çÌÁ×ÎÁ_ÓÔÒÁÎÁ" into
>"%D0%93%D0%BB%D0%B0%D0%B2%D0%BD%D0%B0_%D1%81%D1%82%D1%80%
On 4/13/06, James Bennett <[EMAIL PROTECTED]> wrote:
> Even when I copy/paste that URL (which I had to do, because my
> web-based email client didn't recognize that the Cyrillic portion of
> it was part of the URL) into Firefox, the URL encoding turns
> "çÌÁ×ÎÁ_ÓÔÒÁÎÁ" into
> "%D0%93%D0%BB%D0%B0%D
On 4/13/06, Viktor <[EMAIL PROTECTED]> wrote:
> Of course, every requested url must be URLencoded, but that is browsers
> job, and they all do it quite well.
Except that that runs contrary to the purpose of the slug. See below.
> Yes, they are (more and more every day)... (for example Wikipedia u
gabor wrote:
> and i'm sure you know that those cyrillic slugs, if part of an url will
> get submitted in URLencoded form. even if it is hidden by the browser.
Of course, every requested url must be URLencoded, but that is browsers
job, and they all do it quite well.
> slug = SlugField(only_a
Viktor wrote:
> The problem begins when you want to have nonenglish slug (slug on a
> language that uses nonascii characters).
> For example if I want to have a serban cyrillic slug: наслов_на_српском,
> it is perfectly valid slug if you read it on serbian, just aphanumeric
> characters + under
The problem begins when you want to have nonenglish slug (slug on a
language that uses nonascii characters).
For example if I want to have a serban cyrillic slug: наслов_на_српском,
it is perfectly valid slug if you read it on serbian, just aphanumeric
characters + underscore + hyphen, nothing
Viktor wrote:
> The story about non ASCII characters in slug started in #1602: urlify.js
> blocks out non-English chars.
>
> We tested utf-8 urls against ie, opera and konqueror and they work
> great. Firefox by default shows the urls urlencoded, but you can change:
> network.standard-url
The story about non ASCII characters in slug started in #1602: urlify.js
blocks out non-English chars.
We tested utf-8 urls against ie, opera and konqueror and they work
great. Firefox by default shows the urls urlencoded, but you can change:
network.standard-url.escape-utf8 to false
and
15 matches
Mail list logo
