Losing some space entities
Hi, When I serialize content to HTML5, I lose some entities. xquery: adds '' in front of some content and outputs html html: should have '', but doesn't. I've tried with 8204 and even the half space 8201. The only special space that seems to work is , but it won't do for what I need right now. Code sample: *let* *$target-table* := *copy* *$copy* := *$base-table* *modify*( *for **$td* *in **$copy*//*tr*/*td*[*position*()= *$column-to-filter-by*] *let* *$new-value* := ('', *for **$node* *in **$td*/*node*() *return **$node*) *return replace* *value* *of* *node* *$td* *with **$new-value* ) *return **$copy* *return * *$target-table* Is there any way to solve this? -- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
Hi France, In the database, all Unicode characters will be stored in their standard (decoded) representation. As a result, it is not possible to preserve entities from an original document. For XML serialization via WebDAV, we have one special rule for converting non-breaking spaces (xA0) to entities. Which other Unicode characters would you like to have converted to entities? Cheers, Christian On Fri, Jan 13, 2017 at 7:45 PM, France Baril <france.baril@architextus.com> wrote:
Hi,
When I serialize content to HTML5, I lose some entities.
xquery: adds '' in front of some content and outputs html html: should have '', but doesn't. I've tried with 8204 and even the half space 8201.
The only special space that seems to work is , but it won't do for what I need right now.
Code sample:
let $target-table := copy $copy := $base-table modify( for $td in $copy//tr/td[position()=$column-to-filter-by] let $new-value := ('', for $node in $td/node() return $node) return replace value of node $td with $new-value ) return $copy
return $target-table
Is there any way to solve this?
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
I use - non-breakable space a lot. It's used widely in French. I wanted: - - I've had clients who have asked for the thin space in the past ... I nicely told them 'no'. I've resolved my joiner issue with an alternate solution for now. But if you are opening up the can of worms, and it's not much more work, why not implement all the space and joiner entities to ? Regards, France On Sat, Jan 14, 2017 at 4:34 AM, Christian Grün <christian.gruen@gmail.com> wrote:
Hi France,
In the database, all Unicode characters will be stored in their standard (decoded) representation. As a result, it is not possible to preserve entities from an original document. For XML serialization via WebDAV, we have one special rule for converting non-breaking spaces (xA0) to entities. Which other Unicode characters would you like to have converted to entities?
Cheers, Christian
On Fri, Jan 13, 2017 at 7:45 PM, France Baril <france.baril@architextus.com> wrote:
Hi,
When I serialize content to HTML5, I lose some entities.
xquery: adds '' in front of some content and outputs html html: should have '', but doesn't. I've tried with 8204 and even the half space 8201.
The only special space that seems to work is , but it won't do for what I need right now.
Code sample:
let $target-table := copy $copy := $base-table modify( for $td in $copy//tr/td[position()=$column-to-filter-by] let $new-value := ('', for $node in $td/node() return $node) return replace value of node $td with $new-value ) return $copy
return $target-table
Is there any way to solve this?
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
Hi France,
why not implement all the space and joiner entities to ?
Good idea. I have added even some more characters (see [1]): 8192 – 8207 8232 – 8239 8287 – 8303 A new snapshot (close to the final version 8.6) is online [2]; I’be grateful for some testing feedback! Christian [1] http://docs.basex.org/wiki/WebDAV#Resources [2] http://files.basex.org/releases/latest/
On Sat, Jan 14, 2017 at 4:34 AM, Christian Grün <christian.gruen@gmail.com> wrote:
Hi France,
In the database, all Unicode characters will be stored in their standard (decoded) representation. As a result, it is not possible to preserve entities from an original document. For XML serialization via WebDAV, we have one special rule for converting non-breaking spaces (xA0) to entities. Which other Unicode characters would you like to have converted to entities?
Cheers, Christian
On Fri, Jan 13, 2017 at 7:45 PM, France Baril <france.baril@architextus.com> wrote:
Hi,
When I serialize content to HTML5, I lose some entities.
xquery: adds '' in front of some content and outputs html html: should have '', but doesn't. I've tried with 8204 and even the half space 8201.
The only special space that seems to work is , but it won't do for what I need right now.
Code sample:
let $target-table := copy $copy := $base-table modify( for $td in $copy//tr/td[position()=$column-to-filter-by] let $new-value := ('', for $node in $td/node() return $node) return replace value of node $td with $new-value ) return $copy
return $target-table
Is there any way to solve this?
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
I haven't run many tests yet, but importing the file and exporting the files again from the gui only retains Also, when the entity is in decimal (&8332;), it gets transformed to hex (not a big deal in my book). Other entities are 'applied', but not retained. I'm on BaseX 8.6 beta 4c3daeb On Sun, Jan 15, 2017 at 11:17 AM, Christian Grün <christian.gruen@gmail.com> wrote:
Hi France,
why not implement all the space and joiner entities to ?
Good idea. I have added even some more characters (see [1]):
8192 – 8207 8232 – 8239 8287 – 8303
A new snapshot (close to the final version 8.6) is online [2]; I’be grateful for some testing feedback!
Christian
[1] http://docs.basex.org/wiki/WebDAV#Resources [2] http://files.basex.org/releases/latest/
On Sat, Jan 14, 2017 at 4:34 AM, Christian Grün < christian.gruen@gmail.com> wrote:
Hi France,
In the database, all Unicode characters will be stored in their standard (decoded) representation. As a result, it is not possible to preserve entities from an original document. For XML serialization via WebDAV, we have one special rule for converting non-breaking spaces (xA0) to entities. Which other Unicode characters would you like to have converted to entities?
Cheers, Christian
On Fri, Jan 13, 2017 at 7:45 PM, France Baril <france.baril@architextus.com> wrote:
Hi,
When I serialize content to HTML5, I lose some entities.
xquery: adds '' in front of some content and outputs html html: should have '', but doesn't. I've tried with 8204 and even the half space 8201.
The only special space that seems to work is , but it won't do
for
what I need right now.
Code sample:
let $target-table := copy $copy := $base-table modify( for $td in $copy//tr/td[position()=$column-to-filter-by] let $new-value := ('', for $node in $td/node() return $node) return replace value of node $td with $new-value ) return $copy
return $target-table
Is there any way to solve this?
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
Entities will only be serialized when using WebDAV. Did you try that as well? Am 19.01.2017 12:00 vorm. schrieb "France Baril" < france.baril@architextus.com>: I haven't run many tests yet, but importing the file and exporting the files again from the gui only retains Also, when the entity is in decimal (&8332;), it gets transformed to hex (not a big deal in my book). Other entities are 'applied', but not retained. I'm on BaseX 8.6 beta 4c3daeb On Sun, Jan 15, 2017 at 11:17 AM, Christian Grün <christian.gruen@gmail.com> wrote:
Hi France,
why not implement all the space and joiner entities to ?
Good idea. I have added even some more characters (see [1]):
8192 – 8207 8232 – 8239 8287 – 8303
A new snapshot (close to the final version 8.6) is online [2]; I’be grateful for some testing feedback!
Christian
[1] http://docs.basex.org/wiki/WebDAV#Resources [2] http://files.basex.org/releases/latest/
On Sat, Jan 14, 2017 at 4:34 AM, Christian Grün < christian.gruen@gmail.com> wrote:
Hi France,
In the database, all Unicode characters will be stored in their standard (decoded) representation. As a result, it is not possible to preserve entities from an original document. For XML serialization via WebDAV, we have one special rule for converting non-breaking spaces (xA0) to entities. Which other Unicode characters would you like to have converted to entities?
Cheers, Christian
On Fri, Jan 13, 2017 at 7:45 PM, France Baril <france.baril@architextus.com> wrote:
Hi,
When I serialize content to HTML5, I lose some entities.
xquery: adds '' in front of some content and outputs html html: should have '', but doesn't. I've tried with 8204 and even the half space 8201.
The only special space that seems to work is , but it won't do
for
what I need right now.
Code sample:
let $target-table := copy $copy := $base-table modify( for $td in $copy//tr/td[position()=$column-to-filter-by] let $new-value := ('', for $node in $td/node() return $node) return replace value of node $td with $new-value ) return $copy
return $target-table
Is there any way to solve this?
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
Import works, playing with webdav is giving good results so far. I still want to see how it outputs html through file:write with html5 serialization and if I can retain the entites in my pdfs. That's my next step. On Wed, Jan 18, 2017 at 6:02 PM, Christian Grün <christian.gruen@gmail.com> wrote:
Entities will only be serialized when using WebDAV. Did you try that as well?
Am 19.01.2017 12:00 vorm. schrieb "France Baril" < france.baril@architextus.com>:
I haven't run many tests yet, but importing the file and exporting the files again from the gui only retains Also, when the entity is in decimal (&8332;), it gets transformed to hex (not a big deal in my book). Other entities are 'applied', but not retained.
I'm on BaseX 8.6 beta 4c3daeb
On Sun, Jan 15, 2017 at 11:17 AM, Christian Grün < christian.gruen@gmail.com> wrote:
Hi France,
why not implement all the space and joiner entities to ?
Good idea. I have added even some more characters (see [1]):
8192 – 8207 8232 – 8239 8287 – 8303
A new snapshot (close to the final version 8.6) is online [2]; I’be grateful for some testing feedback!
Christian
[1] http://docs.basex.org/wiki/WebDAV#Resources [2] http://files.basex.org/releases/latest/
On Sat, Jan 14, 2017 at 4:34 AM, Christian Grün < christian.gruen@gmail.com> wrote:
Hi France,
In the database, all Unicode characters will be stored in their standard (decoded) representation. As a result, it is not possible to preserve entities from an original document. For XML serialization via WebDAV, we have one special rule for converting non-breaking spaces (xA0) to entities. Which other Unicode characters would you like to have converted to entities?
Cheers, Christian
On Fri, Jan 13, 2017 at 7:45 PM, France Baril <france.baril@architextus.com> wrote:
Hi,
When I serialize content to HTML5, I lose some entities.
xquery: adds '' in front of some content and outputs html html: should have '', but doesn't. I've tried with 8204 and even the half space 8201.
The only special space that seems to work is , but it won't do
for
what I need right now.
Code sample:
let $target-table := copy $copy := $base-table modify( for $td in $copy//tr/td[position()=$column-to-filter-by] let $new-value := ('', for $node in $td/node() return $node) return replace value of node $td with $new-value ) return $copy
return $target-table
Is there any way to solve this?
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
When I serialize these from a restxq to file with file:write I get the as and as but I get none of the other entities. On Wed, Jan 18, 2017 at 6:59 PM, France Baril <france.baril@architextus.com> wrote:
Import works, playing with webdav is giving good results so far. I still want to see how it outputs html through file:write with html5 serialization and if I can retain the entites in my pdfs. That's my next step.
On Wed, Jan 18, 2017 at 6:02 PM, Christian Grün <christian.gruen@gmail.com
wrote:
Entities will only be serialized when using WebDAV. Did you try that as well?
Am 19.01.2017 12:00 vorm. schrieb "France Baril" < france.baril@architextus.com>:
I haven't run many tests yet, but importing the file and exporting the files again from the gui only retains Also, when the entity is in decimal (&8332;), it gets transformed to hex (not a big deal in my book). Other entities are 'applied', but not retained.
I'm on BaseX 8.6 beta 4c3daeb
On Sun, Jan 15, 2017 at 11:17 AM, Christian Grün < christian.gruen@gmail.com> wrote:
Hi France,
why not implement all the space and joiner entities to ?
Good idea. I have added even some more characters (see [1]):
8192 – 8207 8232 – 8239 8287 – 8303
A new snapshot (close to the final version 8.6) is online [2]; I’be grateful for some testing feedback!
Christian
[1] http://docs.basex.org/wiki/WebDAV#Resources [2] http://files.basex.org/releases/latest/
On Sat, Jan 14, 2017 at 4:34 AM, Christian Grün < christian.gruen@gmail.com> wrote:
Hi France,
In the database, all Unicode characters will be stored in their standard (decoded) representation. As a result, it is not possible to preserve entities from an original document. For XML serialization via WebDAV, we have one special rule for converting non-breaking spaces (xA0) to entities. Which other Unicode characters would you like to have converted to entities?
Cheers, Christian
On Fri, Jan 13, 2017 at 7:45 PM, France Baril <france.baril@architextus.com> wrote:
Hi,
When I serialize content to HTML5, I lose some entities.
xquery: adds '' in front of some content and outputs html html: should have '', but doesn't. I've tried with 8204 and
even
the half space 8201.
The only special space that seems to work is , but it won't do for what I need right now.
Code sample:
let $target-table := copy $copy := $base-table modify( for $td in $copy//tr/td[position()=$column-to-filter-by] let $new-value := ('', for $node in $td/node() return $node) return replace value of node $td with $new-value ) return $copy
return $target-table
Is there any way to solve this?
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com
In XQuery, you can specify entities via output parameters; see the attached example.
When I serialize these from a restxq to file with file:write
I get the as and as but I get none of the other entities.
On Wed, Jan 18, 2017 at 6:59 PM, France Baril <france.baril@architextus.com> wrote:
Import works, playing with webdav is giving good results so far. I still want to see how it outputs html through file:write with html5 serialization and if I can retain the entites in my pdfs. That's my next step.
On Wed, Jan 18, 2017 at 6:02 PM, Christian Grün <christian.gruen@gmail.com> wrote:
Entities will only be serialized when using WebDAV. Did you try that as well?
Hi! This was informative and I'd like to add this example to the BaseX wiki. Could I add it somewhere on the page about Serialization? http://docs.basex.org/wiki/Serialization Thanks Kristian K 19.01.2017 17:04 Christian Grün kirjutas:
In XQuery, you can specify entities via output parameters; see the attached example.
When I serialize these from a restxq to file with file:write
I get the as and as but I get none of the other entities.
On Wed, Jan 18, 2017 at 6:59 PM, France Baril <france.baril@architextus.com> wrote:
Import works, playing with webdav is giving good results so far. I still want to see how it outputs html through file:write with html5 serialization and if I can retain the entites in my pdfs. That's my next step.
On Wed, Jan 18, 2017 at 6:02 PM, Christian Grün <christian.gruen@gmail.com> wrote:
Entities will only be serialized when using WebDAV. Did you try that as well?
Hi Kristian,
This was informative and I'd like to add this example to the BaseX wiki. Could I add it somewhere on the page about Serialization?
Edits are always welcome! Thanks in advance, Christian
http://docs.basex.org/wiki/Serialization
Thanks Kristian K
19.01.2017 17:04 Christian Grün kirjutas:
In XQuery, you can specify entities via output parameters; see the attached example.
When I serialize these from a restxq to file with file:write
I get the as and as but I get none of the other entities.
On Wed, Jan 18, 2017 at 6:59 PM, France Baril <france.baril@architextus.com> wrote:
Import works, playing with webdav is giving good results so far. I still want to see how it outputs html through file:write with html5 serialization and if I can retain the entites in my pdfs. That's my next step.
On Wed, Jan 18, 2017 at 6:02 PM, Christian Grün <christian.gruen@gmail.com> wrote:
Entities will only be serialized when using WebDAV. Did you try that as well?
I tried my best at http://docs.basex.org/wiki/Serialization#Character_mappings Cheers Kristian 20.01.2017 18:54 Christian Grün kirjutas:
Hi Kristian,
This was informative and I'd like to add this example to the BaseX wiki. Could I add it somewhere on the page about Serialization? Edits are always welcome!
Thanks in advance, Christian
http://docs.basex.org/wiki/Serialization
Thanks Kristian K
19.01.2017 17:04 Christian Grün kirjutas:
In XQuery, you can specify entities via output parameters; see the attached example.
When I serialize these from a restxq to file with file:write
I get the as and as but I get none of the other entities.
On Wed, Jan 18, 2017 at 6:59 PM, France Baril <france.baril@architextus.com> wrote:
Import works, playing with webdav is giving good results so far. I still want to see how it outputs html through file:write with html5 serialization and if I can retain the entites in my pdfs. That's my next step.
On Wed, Jan 18, 2017 at 6:02 PM, Christian Grün <christian.gruen@gmail.com> wrote:
Entities will only be serialized when using WebDAV. Did you try that as well?
participants (3)
-
Christian Grün -
France Baril -
Kristian Kankainen