Masayuki Nakano wrote:
> [EMAIL PROTECTED] wrote:
>> I really want to find out what the jp-critical need for linebreaking
>> of Latin-1 text is.
>
> we need to break URLs in most cases, therefore, I think, we should break
> after '/' for path part of URLs. And also we should break after '\' for
> windows file path too. And we should also break after '&' and ';' or '='
> for param part of URLs. And '%' too. It is used for %-encoding.
Why do we "need to" break URLs? Yes, it would be nice but can you give
some examples of where this is "jp-critical"? It would be better if we
all had the same understanding of the problem we're trying to solve here.
I'd rather not break at '\', because it is used in escapes, which could
be in the middle of a token. If we're breaking at '\', I want to see
examples of why it is necessary and some estimate of how common these
cases are vs. the cases where we want the word to stay together.
For %-encoding, you'd want to break *before* the %, not after it. But
for normal usage, e.g. '100%', you really don't want to break before.
Therefore I don't think % should be a breaking character.
I don't see a problem with breaking after ';'. I can't recall how they're
particularly relevant to URLs, but I also can't think of any cases where
that would break anything.
If we want to break at &, then we should prioritize spaces and semicolons
over &. We don't want 'x &nbps; ' to break after either &.
> '/' and '\' may be needed the context analysis. (they are only broken
> after if it is second or more?)
Yes, I believe this is necessary. 'c/o' should never break. Neither should
'\n'. If we're allowing breaks at slashes in 1.9, then this level of context
analysis is imho required.
> I'm thinking for other patters, but I think it's enough.
>
> *However*, if nobody have trouble, we should use similar spec for the
> compatibility with WinIE. I.e., '!', '$', '?', '[', ']', '{', '}', '¢'
> and '°'.
I think we should avoid introducing breaks until we have thought through
all the consequences, which I'm not convinced we have for most of these
breaks. Compatibility with WinIE is not "thought through all the
consequences".
~fantasai
_______________________________________________
dev-tech-layout mailing list
dev-tech-layout@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-layout
