As reported in a separate thread, I’m still getting the optimization failure
for large databases but not smaller ones. This behavior is consistent in my
tests.
Cheers,
E.
_
Eliot Kimber
Sr Staff Content Engineer
O: 512 554 9368
M: 512 554 9368
Now that I’m using an expected extension, a bit more feedback on the Editor UI.
Having saved a file and then not modified what’s in the editor, opening a new
file should not prompt for confirmation as the editor isn’t “dirty” and there
can be no data loss (the contents of the editor were just
Using BaseX 11 (but I think the code is the same in BaseX 10).
I’m trying to understand how base-uri() behaves relative to how it should
behave when the database path of a document is not a valid URI, i.e., it has a
space in it.
First I have this test:
let $doc as document-node() := document
…just a quick reply: That’s probably related to [1], an ancient issue, in
which I tended to recommend the usage of db:path. I wish we’d finally find
time and ressources to tackle this.
[1] https://github.com/BaseXdb/basex/issues/1172
On Mon, Mar 4, 2024 at 11:49 AM Eliot Kimber
wrote:
> Using
Oh right—I submitted that issue 9 years ago !
Any solution will be challenging due to the age of the current behavior and the
twisty nature of the code.
My use of @xml:base may be somewhat singular as it’s specific to the way that
DITA works and I don’t know that there is any other XML
…thanks; we’ve added some usability tweaks in the editor.
On Mon, Mar 4, 2024 at 11:15 AM Eliot Kimber
wrote:
> Now that I’m using an expected extension, a bit more feedback on the
> Editor UI.
>
>
>
> Having saved a file and then not modified what’s in the editor, opening a
> new file should
6 matches
Mail list logo