Recent changes to feature-requests

CQPweb: more elaborate customisable header for corpus homepage

2024-06-10T20:29:24.573000Z

A user requests the ability to specikfy more elaborate content for the right-panel area in the corpus query-home interface.

That should include, e.g. arbitrary HTML /CSS formatting including image files.

Since this could have wide application, it will be done but is not urgent. It will be implemented in the novel HTML generator object model.

CQPweb: per-user tabulation templates

2023-11-14T14:40:07.666000Z

Add the possibility to create templates for frequency used tabulation settings. Then display them alongside the detailed controls.

#72 XML output mode for CQP

2023-10-21T20:53:33.134000Z

No there's not, because it's (a) really far in the future and (b) not going to be remotely difficult when we actually get there.

#72 XML output mode for CQP

2023-10-21T18:08:48.478000Z

Yes, I had to found a work around the attribute separator. My suggestion about FreeLing was mainly for the possibility to display the token and its attributes as nodes, instead of plain text. But it seems it implies a lot of fixes and that is something that is going to be fix in version 4. Is that the case, is there any draft for the XML output?

#72 XML output mode for CQP

2023-10-15T07:40:47.917000Z

A kwic concordance (where left and right context might not even contain complete tokens!) is very different from a list of sentences with pre-determined annotation as in the FreeLing output. I don't think we can learn much from it to help us address the challenges of kwic XML output.

SGML print mode is really badly broken if you display s-attributes in the concordance. It also includes them (and any p-attributes) as plain text in the tokens rather than in a way that allows them to be processed e.g. with XSLT.

#72 XML output mode for CQP

2023-10-14T18:44:35.820000Z

About the DTD, I will use the same SGML structure but XML compliant. For more ideas about the schema, FreeLing output formats could be an useful resource.

#72 XML output mode for CQP

2023-10-14T18:27:48.254000Z

Note to those not familiar with CQP print modes: Their implementation is a horrible mess, so we are reluctant to add extensions and very limited in what can be achieved. Moreover, the print modes only affect some CQP output (kwic concordances, frequency tables from group) but by far not all.

#72 XML output mode for CQP

2023-10-14T18:25:46.414000Z

Description has changed:

Diff:

--- old
+++ new
@@ -1 +1,3 @@
-Hi, I am opening this request as indicated in https://sourceforge.net/p/cwb/bugs/80/
+This request originates from https://sourceforge.net/p/cwb/bugs/80/: The desire is to have add an XML print mode to CQP that always generates valid XML.
+
+The DTD for this print mode is entirely unclear, so suggestions (in comments below) are very welcome.

assigned_to: Stephanie Evert
Group: TODO-3.5 --> TODO-3.6
Priority: 5 --> 6

XML output mode for CQP

2023-10-14T17:52:27.851000Z

Hi, I am opening this request as indicated in https://sourceforge.net/p/cwb/bugs/80/

XML output mode for CQP

2023-10-14T17:52:27.851000Z

Ticket 72 has been modified: XML output mode for CQP
Edited By: Stephanie Evert (schtepf)
_milestone updated: 'TODO-3.5' => 'TODO-3.6'
_priority updated: '5' => '6'
Owner updated: None => 'schtepf'
Description updated:
--- description-old

+++ description-new

@@ -1 +1,3 @@

-Hi, I am opening this request as indicated in https://sourceforge.net/p/cwb/bugs/80/
+This request originates from https://sourceforge.net/p/cwb/bugs/80/: The desire is to have add an XML print mode to CQP that always generates valid XML.
+
+The DTD for this print mode is entirely unclear, so suggestions (in comments below) are very welcome.