Re: [openvrml-develop] urls and non-ascii filenames

[Braden M. <br...@en...>]

On Wed, 2010-09-29 at 18:27 +0200, supplier wrote: 
> Hello,
> 
>  
> 
> We are using openvrml to load wrl-customer-data into our
> visualization-software using our own rendering.
> 
>  
> 
> There's now another issue here on my desk dealing with filenames using
> non-ascii characters. Generally, we use wide-character strings here to
> identify local filenames.
> 
>  
> 
> I guess to be able to load such files using openvrml::browser's
> load_url() I would have to encode the names accordingly to common
> url-conventions just using ascii-chars, and decode them later in my own
> ressource-fetcher on file-access. Is this correct?

Pretty much.

> If so, can I use any
> tools (encode/decode) here within your API to get through easier?

There's nothing like this in OpenVRML's API.

Presumably you're starting from Windows UTF-16.  You probably want to
first convert to UTF-8; then URI-encode any non-ASCII octets and URI
reserved characters.

> I'm not too familiar with url-convention(s); what exactly do you expect
> here?

A valid URI, as specified by RFC 3986:

        http://www.apps.ietf.org/rfc/rfc3986.html

The grammar in Appendix A may be the most helpful bit.

(And truth be told, current OpenVRML really reflects this
specification's predecessor, RFC 2396.  The only major difference is the
addition of the IPv6 bits in 3986.  Support for that will be added when
I update OpenVRML to use Spirit 2.x.)

-- 
Braden McDaniel <br...@en...>