Hi Christoph, and list,
Thank you for your quick reference.
Just as a follow up on this, for other people, a path like:
/ja/2005report1
would really need just the first character of 2005report1 to be
encoded to be properly searched. So that would give us and xpath
query like:
//ja/PressRelease/_x0032_005report1
Note also that the hexa decimal needs to be on four digits.
One last note, encoding the whole name in hexa doesn't work. Each
hexa character would need to be surrounded by the "_x" and "_"
characters.
So in our example, the xpath would be the following:
//ja/PressRelease/_x0032__x0030_05report1
Hope that this can help someone in the future.
As Jan Kuźniak noted last december, it would be really great if this
was transparent.
Thanks again,
Nicolas,
On Jun 28, 2007, at 5:23 PM, Christoph Kiehl wrote:
Nicolas Modrzyk wrote:
The path containing a name within the path starting with an
integer is causing troubles. I can reproduce this reliably.
See http://www.nabble.com/Re%3A-Node-name-starting-with-number-
problem-p7639960.html
BR,
Christoph
