On 10/09/07 02:54, Masayuki Nakano wrote:

> hmm... I'm not sure it is problem. I think there are two patterns when 
> you paste/write the URIs.
> 
> 1. URI is a independent.
> 
> I.e., URI is an only member of a paragraph. In western context, we use 
> empty line for paragraph separator. So, the wrapped URI doesn't make any 
> confusing.
> 
> 2. URI is a word.
> 
> I.e., URI is an inline word of paragraph. In old layout, the URI was a 
> line. Now, the URI might be separated two or more lines. But there are 
> really word separators around URI. So, the URI is always an independent 
> word. (And other browsers have same behavior, but I don't know the 
> objections for it.)
> 
> I cannot understand what is problem. Note that Japanese text is 
> breakable in most points, so the broken words are natural things for me...

The difference between words (in western languages) and URLs is that if
you break a word you have a continuation character (the '-') that signifies
that this word continues on the next line. This special character is very
visible because it stands out in normal text where most of the characters
are alphabetic. For URLs you don't have that, at least not a unique one.
And because URLs (and file paths) can contain all kinds of special
characters and numbers in addition to alphabetic characters the eye is
already distracted enough and doesn't easily notice line breaks.

The worst examples are the long URLs that some people using Apple Mail send
to the .planning newsgroup[1]. Granted, Apple Mail wrapping is much worse, you
have done much better work. But let's say you want to send something about
fixed bugs https://bugzilla.mozilla.org/buglist.cgi?keywords=fixed1.8.1.8&;
order=bugs.bug_id and you find some rubbish at the beginning of the line
where it's difficult to at first glance where that comes from. It gets even
worse when someone now quotes this part[2]. If the URL would not be broken,
perhaps like this 
https://bugzilla.mozilla.org/buglist.cgi?keywords=fixed1.8.1.8&order=bugs.bug_id
it would be clear immediately where it stopped, even though it might not be
as beautiful because something extends outside the width of the normal text.

Note that I am not arguing to switch the standard behavior. As Boris says
most people may get used to it eventually. But for myself and the people who
don't, I would like to be able to decide not to break URLs at all (perhaps
by some hidden pref). If I would get an indication that this would be taken
up I could try to make a patch for that.

   Peter.

[1] e.g. Message-ID: <[EMAIL PROTECTED]>
    or <[EMAIL PROTECTED]>
[2] Message-ID: <[EMAIL PROTECTED]>
    or <[EMAIL PROTECTED]>

_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout

Reply via email to