bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Spaces in filenames break point-and-click with Mac OS X Preview


From: Ed Baskerville
Subject: Re: Spaces in filenames break point-and-click with Mac OS X Preview
Date: Wed, 24 Aug 2005 11:19:17 -0700

When in doubt: check the spec. I did this, and found that Adobe's PDF spec refers you to RFC 2396 (http://www.ietf.org/rfc/rfc2396.txt), which contains the following:

2.4.2. When to Escape and Unescape

A URI is always in an "escaped" form, since escaping or unescaping a
   completed URI might change its semantics.  Normally, the only time
escape encodings can safely be made is when the URI is being created
   from its component parts; each component may have its own set of
   characters that are reserved, so only the mechanism responsible for
   generating or interpreting that component can determine whether or
   not escaping a character will change its semantics. Likewise, a URI
   must be separated into its components before the escaped characters
   within those components can be safely decoded.

[...]

2.4.3. Excluded US-ASCII Characters

Although they are disallowed within the URI syntax, we include here a description of those US-ASCII characters that have been excluded and
   the reasons for their exclusion.

[...]

   The space character is excluded because significant spaces may
   disappear and insignificant spaces may be introduced when URI are
   transcribed or typeset or subjected to the treatment of word-
processing programs. Whitespace is also used to delimit URI in many
   contexts.

   space       = <US-ASCII coded character 20 hexadecimal>

It looks like Acrobat is just adhering to the intelligent approach of being tolerant of malformed data, while Preview is not. Since Apple is, technically speaking, not violating the spec, I don't imagine they'll be in a hurry to match Acrobat's behavior (though it would be smart to do so).

Conclusion: it should be fixed in LilyPond.

--Ed

On Aug 24, 2005, at 2:47 AM, Han-Wen Nienhuys wrote:

Ed Baskerville wrote:

Does this work properly on other systems? Should I file a bug asking Apple to support non-percent-escaped URIs, or are they following the standard?


AFAIK, apple has messed up. Acrobat does fine. The URIs should be escaped before being sent to the browser. I actually filed a bug with apple, but they are disappointingly lax with fixing problems.

--
 Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen






reply via email to

[Prev in Thread] Current Thread [Next in Thread]