Search Mailing List Archives
[p4-feedback] Rendering of URI fragments that contains escaped characters
nick.drummond at cs.manchester.ac.uk
Tue Apr 21 08:08:36 PDT 2009
I've fixed the QName renderer.
Not sure the best behaviour of the rename dialog - I figure plenty of people
are going to want to type characters straight in so it should display the
decoded one and encode on OK (which it currently doesn't do).
I would appreciate feedback on this though.
2009/4/19 S Essaid <sielists at gmail.com>
> I have a script that creates individuals and few of the individuals' URI
> fragments would look like "#ImageMediaType_image/jpeg" so I encoded the
> forward slash by replacing it with %2F. Following are few issues I noticed
> about how Protege 4 handles these URIs.
> If I set entity rendering to URI fragment then the encoding is *decoded*and the GUI label would be "ImageMediaType_image/jpeg". This is how I want
> the labels to appear to users.
> If I set entity rendering to qnames then the encoding is *not decoded* and
> the GUI label would be "prefix:ImageMediaType_image%2Fjpeg". Not very easy
> to read. I would like the qname labels to also be decoded for display.
> If I try the "Change Entity URI" refactoring tool the tool decodes the URI
> to "ImageMediaType_image/jpeg" instead of showing the original fragment. I
> can still enter an encoded fragment but I thought that the field should show
> the original fragment not a decoded one. The original fragment name will be
> changed even if just click the OK button without making any changes to the
> displayed fragment.
> Are these behaviours intentional?
> I am using P4 build 110 with included JVM on Windows XP
> Thank you,
> p4-feedback mailing list
> p4-feedback at lists.stanford.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the p4-feedback