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 ___________________________

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 this</p>

It appears that files are saved correctly, because this query returns the p element: for $x in //text()[contains(., ' ')] return $x/parent::*.

However, when we reopen the file in BaseX, the   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   character.

-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com (514) 572-0341

_______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk