[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
At 2008-10-16 15:12 +0100, Andrew Welch wrote:
Not sure what you mean by "minimization" in this case.
But I will comment on using such Unicode characters. In my UBL work I peppered my URI strings with zero-width (breaking) spaces in order to elegantly wrap lines immediately after slashes, keeping URI path components whole. Some users had not taken the time to add Unicode character display to their browsers (not sure if that is now automatic but at one point browsers didn't do all Unicode characters until you consciously installed Unicode support).
The result were unsightly empty box glyphs after every slash on their screens, while my screen looked pristine.
So before you use any Unicode character you should find out what the rendition looks like on a browser without Unicode character support.
I hope this helps.
. . . . . . . . . . . Ken
Re: [xsl] zero width no-break space to prevent tag minimisation
Subject: Re: [xsl] zero width no-break space to prevent tag minimisation From: "G. Ken Holman" <gkholman@xxxxxxxxxxxxxxxxxxxx> Date: Thu, 16 Oct 2008 10:21:08 -0400 |
At 2008-10-16 15:12 +0100, Andrew Welch wrote:
Can anyone see any issues with using a "zero with no-break space" (the BOM) as a way of preventing tag minimization:
<div></div>
It seems to work - any reason I shouldn't use that? Using a breaking (breakable?) zero width space (#8203) doesn't seem to prevent the minimisation...
(the usual techniques of a comment or #160 can't be used in this particular case)
Not sure what you mean by "minimization" in this case.
But I will comment on using such Unicode characters. In my UBL work I peppered my URI strings with zero-width (breaking) spaces in order to elegantly wrap lines immediately after slashes, keeping URI path components whole. Some users had not taken the time to add Unicode character display to their browsers (not sure if that is now automatic but at one point browsers didn't do all Unicode characters until you consciously installed Unicode support).
The result were unsightly empty box glyphs after every slash on their screens, while my screen looked pristine.
So before you use any Unicode character you should find out what the rendition looks like on a browser without Unicode character support.
I hope this helps.
. . . . . . . . . . . Ken
-- Upcoming XSLT/XSL-FO hands-on courses: Wellington, NZ 2009-01 Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video Video sample lesson: http://www.youtube.com/watch?v=PrNjJCh7Ppg Video course overview: http://www.youtube.com/watch?v=VTiodiij6gE G. Ken Holman mailto:gkholman@xxxxxxxxxxxxxxxxxxxx Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ Male Cancer Awareness Nov'07 http://www.CraneSoftwrights.com/s/bc Legal business disclaimers: http://www.CraneSoftwrights.com/legal
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] zero width no-break space, Michael Kay | Thread | Re: [xsl] zero width no-break space, Andrew Welch |
RE: [xsl] zero width no-break space, Michael Kay | Date | Re: [xsl] zero width no-break space, Andrew Welch |
Month |
Keywords