Main Page » Mailing List » August 2013

Losing non-breakable spaces ( )

Sunday, 18 August 2013 · 2 messages
CG
Christian Grünin reply to France Baril, 18 Aug 2013, 02:0718 Aug 2013 00:59 #
Hi France, my assumption is that, when a document is stored in the database, non-breakable spaces are replaced with the equivalent Unicode characters, which cannot be distinguished from simple spaces in the editor (" " vs. " ". The reason is that all entities are normalized and resolved before they are stored in the database, and all characters are then serialized as Unicode. Please correct me if you believe I’m wrong. Christian
Quoted text · France Baril · 29 lines
> We are using a BaseX HTTP server (still on version 7.6), accessing files via > WebDAV for authoring in XML Oxygen. > > At some point in the process, we lose our non-breakable spaces. > > If Isave a file with this content in BaseX: <p>Test&#160;this</p> > > It appears that files are saved correctly, because this query returns the p > element: for $x in //text()[contains(., '&#160;')] > return $x/parent::*. > > However, when we reopen the file in BaseX, the &#160; has been replaced by a > space. > > We tried the same experiment saving and opening the file on the file system > to make sure the issue wasn't with XML Oxygen. The file reopens with the > correct &#160; character. > > -- > France Baril > Architecte documentaire / Documentation architect > france.baril at architextus.com > (514) 572-0341 > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >
FB
France Baril18 Aug 2013 02:07 #
Hi, We are using a BaseX HTTP server (still on version 7.6), accessing files via WebDAV for authoring in XML Oxygen. At some point in the process, we lose our non-breakable spaces. If Isave a file with this content in BaseX: <p>Test&#160;this</p>
It appears that files are saved correctly, because this query returns the p
element: for $x in //text()[contains(., '&#160;')]
             return $x/parent::*.
However, when we reopen the file in BaseX, the &#160; has been replaced by a space. We tried the same experiment saving and opening the file on the file system to make sure the issue wasn't with XML Oxygen. The file reopens with the correct &#160; character.
-- France Baril Architecte documentaire / Documentation architect france.baril at architextus.com (514) 572-0341

Written for BaseX 7.7. BaseX may have changed since: please check the current documentation.

⚡Generated with XQuery