BaseX 10.7: The Summer Edition
Friday, 4 August 2023 · 5 messages · last reply 9 Aug 2023
CG
Christian Grün4 Aug 2023 12:54 #
Dear all,
We’re pleased to announce version 10.7 of BaseX, of our XML framework: https://basex.org.
The new release is a big step forward towards BaseX 11:
• We have added numerous new operators, functions and features of XQuery 4.
• The GUI editor and result view now provide full support for Unicode characters.
• Font rendering has been improved (you can tweak it in the Font Dialog)
• More BaseX 11 preview features available (see docs.basex.org)
• Various bug fixes (
web:forward, job:eval, main-memory documents)
Have fun,
Your BaseX TeamML
Marco Lettere4 Aug 2023 17:13 #
GREAT!!!!
Big thanks!
Quoted text · Christian Grün · 19 lines
On 04/08/23 12:54, Christian Grün wrote: > Dear all, > > We’re pleased to announce version 10.7 of BaseX, of our XML framework: > https://basex.org. > > The new release is a big step forward towards BaseX 11: > > • We have added numerous new operators, functions and features of > XQuery 4. > • The GUI editor and result view now provide full support for Unicode > characters. > • Font rendering has been improved (you can tweak it in the Font Dialog) > • More BaseX 11 preview features available (see docs.basex.org > <http://docs.basex.org>) > • Various bug fixes (web:forward, job:eval, main-memory documents) > > Have fun, > Your BaseX Team
CG
Christian Grün7 Aug 2023 12:03 #
Hi Yitzhak,
The documentation in our wiki will be made available with version 11, but you can already browse through the current drafts of the specifications. Many of the listed features are already working:
https://qt4cg.org/specifications/xpath-functions-40/Overview.html#changelog https://qt4cg.org/specifications/xquery-40/xquery-40.html#id-revision-log
Hope this helps,
Christian
Quoted text · AM · 20 lines
On Sun, Aug 6, 2023 at 3:53 AM <ykhabins at bellsouth.net> wrote: > Congrats on the new BaseX 10.7 release! > > > > >> “We have added numerous new operators, functions and features of XQuery 4.“ > > How to find that new XQuery 4 functionality in the BaseX wiki? > > Is their a particular keyword for that? > > > > > > > *Regards,Yitzhak Khabinsky* > > >
TT
Congrats on the latest version! Looking forward as usual to exploring the new features.
However, I'm perplexed by the decision to remove the text parser from the codebase. I understand the desire to streamline and remove dependencies related to lower-value features, but I've always found the text parser to be super useful. After installing Basex 10.8 beta today, I had to refactor a process (parsing a set of interview transcripts generated by Zoom) that involved creating a DB from a directory of text files.
In addition, I noticed some unexpected results in how the text was parsed using standard methods. In BaseX 10.6, using the text parser in the GUI, the output looks like this:
<text>WEBVTT1
00:00:02.910 --> 00:00:27.240
...
</text>
Here, each line end is just a newline character (\n).
Using
file:read-text or fn:unparsed-text (in 10.6 and 10.8 beta), the output looks like this:<text>WEBVTT

1
00:00:02.910 --> 00:00:27.240
...
</text>Here, each line end also has a carriage return (\r).
And if instead, I store it as an XQuery value, I see the newline characters that aren't otherwise displayed in the GUI:
"WEBVTT

1
00:00:02.910 -->
00:00:27.240
..."
So, the text parser seems to have done some normalization, which was also helpful.
Any chance that it could be restored (by popular demand) in version 11? :)
Best regards,
Tim
--
Tim A. Thompson (he, him)
Librarian for Applied Metadata Research
Yale University Library
Quoted text · Christian Grün (christian.gruen at gmail.com) · 20 lines
El vie, 4 ago 2023 a la(s) 06:55, Christian Grün (christian.gruen at gmail.com) escribió: > Dear all, > > We’re pleased to announce version 10.7 of BaseX, of our XML framework: > https://basex.org. > > The new release is a big step forward towards BaseX 11: > > • We have added numerous new operators, functions and features of XQuery > 4. > • The GUI editor and result view now provide full support for Unicode > characters. > • Font rendering has been improved (you can tweak it in the Font Dialog) > • More BaseX 11 preview features available (see docs.basex.org) > • Various bug fixes (web:forward, job:eval, main-memory documents) > > Have fun, > Your BaseX Team >
CG
Christian Grün9 Aug 2023 10:42 #
Hi Tim,
I’m sorry that we dropped the text parser feature in BaseX. It didn’t really fit into the existing parser concept, which we want to further streamline in future releases. If enough people are interested, we could re-introduce a comparable functionality in a future version.
As of now, you can use fn:read-text-lines or
fn:unparsed-text-lines:let $file := 'file.txt'
return db:create(
'db',
element text { file:read-text-lines($file) ! element line { . } },
$file
)The handling of newlines in
fn:unparsed-text will possibly be improved in XQuery 4 [1]; feel free to add your suggestions to this issue or others.
Hope this helps,
Christian
[1] https://github.com/qt4cg/qtspecs/issues/216Quoted text · Tim Thompson · 50 lines
On Wed, Aug 9, 2023 at 4:23 AM Tim Thompson <timathom at gmail.com> wrote: > Congrats on the latest version! Looking forward as usual to exploring the > new features. > > However, I'm perplexed by the decision to remove the text parser from the > codebase. I understand the desire to streamline and remove dependencies > related to lower-value features, but I've always found the text parser to > be super useful. After installing Basex 10.8 beta today, I had to refactor > a process (parsing a set of interview transcripts generated by Zoom) that > involved creating a DB from a directory of text files. > > In addition, I noticed some unexpected results in how the text was parsed > using standard methods. In BaseX 10.6, using the text parser in the GUI, > the output looks like this: > > <text>WEBVTT > > 1 > 00:00:02.910 --> 00:00:27.240 > ... > </text> > > Here, each line end is just a newline character (\n). > > Using file:read-text or fn:unparsed-text (in 10.6 and 10.8 beta), the > output looks like this: > > <text>WEBVTT
 > 
 > 1
 > 00:00:02.910 --> 00:00:27.240
 > ... > </text> > > Here, each line end also has a carriage return (\r). > > And if instead, I store it as an XQuery value, I see the newline > characters that aren't otherwise displayed in the GUI: > > "WEBVTT

1
00:00:02.910 --> 00:00:27.240
..." > > So, the text parser seems to have done some normalization, which was also > helpful. > > Any chance that it could be restored (by popular demand) in version 11? :) > > Best regards, > Tim > >
Written for BaseX 10.7. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery