From tgraham at antenna.co.jp Wed Aug 4 11:46:26 2021
From: tgraham at antenna.co.jp (Tony Graham)
Date: Wed, 4 Aug 2021 17:46:26 +0100
Subject: [oXygen-user] '# ' in Markdown editor
Message-ID:
Please open:
https://raw.githubusercontent.com/AntennaHouse/focheck/master/README.md
The '' causes Oxygen 23.1 to preview the following text
as if it's all , and the following titles get even bigger. I don't
observe this happening in Oxygen Author 18.1.
Is there a Markdown workaround that still does the right thing on GitHub?
Regards,
Tony Graham.
--
Senior Architect
XML Division
Antenna House, Inc.
----
Skerries, Ireland
tgraham at antenna.co.jp
From support at oxygenxml.com Thu Aug 5 00:09:09 2021
From: support at oxygenxml.com (Oxygen XML Editor Support (Radu Coravu))
Date: Thu, 5 Aug 2021 08:09:09 +0300
Subject: [oXygen-user] '# ' in Markdown editor
In-Reply-To:
References:
Message-ID:
Hi Tony,
Thanks for the report, I added an internal issue to look into fixing this.
From version to version we might update the libraries which parse
Markdown, we have also our own functionality which attempts to add some
backmapping between the edited Markdown and the HTML preview, I suspect
there is a bug on our side.
The "DITA" preview looks Ok though.
I also notices that in Oxygen's Markdown editor there is some red
foreground around one of your links which you made bold:
> - **focheck** はサブモジュールとして
> **[stf](https://github.com/Schematron/stf)**
I added an internal issue to have that sorted out as well.
Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 8/4/21 19:46, Tony Graham wrote:
> Please open:
>
> https://raw.githubusercontent.com/AntennaHouse/focheck/master/README.md
>
> The '' causes Oxygen 23.1 to preview the following text
> as if it's all , and the following titles get even bigger. I don't
> observe this happening in Oxygen Author 18.1.
>
> Is there a Markdown workaround that still does the right thing on GitHub?
>
> Regards,
>
>
>
> Tony Graham.
From yves.barbion at gmail.com Thu Aug 5 02:46:04 2021
From: yves.barbion at gmail.com (Yves Barbion)
Date: Thu, 5 Aug 2021 09:46:04 +0200
Subject: [oXygen-user] xref to fig displays ID in responsive webhelp output
Message-ID:
Hi group
I've got this topic:
test
See
When I generate HTML5 output (using OxygenXML Editor version 23.1), all is
well: I see "See Figure 1". When I generate the default responsive output,
however, I see the ID of the fig displayed, so "See #test/fig_nmn_q1s_mqb".
Any idea how this can be fixed?
Thanks
Yves
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From tgraham at antenna.co.jp Thu Aug 5 16:12:39 2021
From: tgraham at antenna.co.jp (Tony Graham)
Date: Thu, 5 Aug 2021 22:12:39 +0100
Subject: [oXygen-user] '# ' in Markdown editor
In-Reply-To:
References:
Message-ID: <260f61aa-4271-8265-bd44-18f51e6c9794@antenna.co.jp>
Radu,
On 05/08/2021 06:09, Oxygen XML Editor Support (Radu Coravu) wrote:
> Thanks for the report, I added an internal issue to look into fixing this.
...
> I added an internal issue to have that sorted out as well.
Thanks, twice over.
Regards,
Tony Graham.
--
Senior Architect
XML Division
Antenna House, Inc.
----
Skerries, Ireland
tgraham at antenna.co.jp
From support at oxygenxml.com Fri Aug 6 04:50:51 2021
From: support at oxygenxml.com (Oxygen XML Editor Support (Ionela Istodor))
Date: Fri, 6 Aug 2021 12:50:51 +0300
Subject: [oXygen-user] xref to fig displays ID in responsive webhelp
output
In-Reply-To:
References:
Message-ID:
Hi Yves,
To get the same result also for the WebHelp Responsive output you need
to set 'args.figurelink.style' parameter to 'NUMTITLE'.
This can be set either in the WebHelp Responsive transformation scenario
(Parameters tab) or in the Publishing Template descriptor file (*.opt).
Regards,
Ionela
--
Ionela Istodor
oXygen XML Editor and Author Support
Tel: +1-650-352-1250 ext.3010
Fax: +40-251-461482
support at oxygenxml.com
http://www.oxygenxml.com
---------------------------------------------------------------------------
This message (including any attachments) contains confidential information and is intended only for the individual(s) named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Any quotation contained herein has a validity of 30 days, unless otherwise specified. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
On 8/5/2021 10:46 AM, Yves Barbion wrote:
> Hi group
>
> I've got this topic:
>
>
>
>
> test
>
> See
>
>
>
>
>
>
> When I generate HTML5 output (using OxygenXML Editor version 23.1),
> all is well: I see "See Figure 1". When I generate the default
> responsive output, however, I see the ID of the fig displayed, so "See
> #test/fig_nmn_q1s_mqb".
>
> Any idea how this can be fixed?
>
> Thanks
>
> Yves
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From yves.barbion at gmail.com Fri Aug 6 07:21:11 2021
From: yves.barbion at gmail.com (Yves Barbion)
Date: Fri, 6 Aug 2021 14:21:11 +0200
Subject: [oXygen-user] xref to fig displays ID in responsive webhelp
output
In-Reply-To:
References:
Message-ID:
Hi Ionela
Aha! Yes, setting "args.figurelink.style" to NUMBER or NUMTITLE solved the
problem. The xrefs to the fig now display "Figure 1", "Figure 2" etc.
The figures themselves, however, are not numbered yet. So when I have
multiple figs on one page, they all just have the label "Figure:" and no
number in my Oxygen responsive webhelp output. In the HTML5 output however,
the figures are numbered. Any idea how I can number my figures in my
webhelp just like in the HTML5?
Sorry, but my knowledge of css and xsl is rather limited.
Thank you very much.
Yves
On Fri, 6 Aug 2021 at 12:11, Oxygen XML Editor Support (Ionela Istodor) <
support at oxygenxml.com> wrote:
> Hi Yves,
>
> To get the same result also for the WebHelp Responsive output you need to
> set 'args.figurelink.style' parameter to 'NUMTITLE'.
> This can be set either in the WebHelp Responsive transformation scenario
> (Parameters tab) or in the Publishing Template descriptor file (*.opt).
>
> Regards,
> Ionela
>
> --
> Ionela Istodor
> oXygen XML Editor and Author Support
>
> Tel: +1-650-352-1250 ext.3010
> Fax: +40-251-461482support at oxygenxml.comhttp://www.oxygenxml.com
>
>
> ---------------------------------------------------------------------------
> This message (including any attachments) contains confidential information and is intended only for the individual(s) named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Any quotation contained herein has a validity of 30 days, unless otherwise specified. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
>
> On 8/5/2021 10:46 AM, Yves Barbion wrote:
>
> Hi group
>
> I've got this topic:
>
>
>
>
> test
>
> See
>
>
>
>
>
>
> When I generate HTML5 output (using OxygenXML Editor version 23.1), all is
> well: I see "See Figure 1". When I generate the default responsive output,
> however, I see the ID of the fig displayed, so "See #test/fig_nmn_q1s_mqb".
>
> Any idea how this can be fixed?
>
> Thanks
>
> Yves
>
> _______________________________________________
> oXygen-user mailing listoXygen-user at oxygenxml.comhttps://www.oxygenxml.com/mailman/listinfo/oxygen-user
>
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From support at oxygenxml.com Mon Aug 16 03:00:20 2021
From: support at oxygenxml.com (Oxygen XML Editor Support (Julien Lacour))
Date: Mon, 16 Aug 2021 11:00:20 +0300
Subject: [oXygen-user] xref to fig displays ID in responsive webhelp
output
In-Reply-To:
References:
Message-ID:
Hello Yves,
The figure number is filtered in WebHelp output by the following CSS rule:
.fig--title-label-number,
.fig--title-label-punctuation {
display:none;
}
If you want it in your output, simply create a custom CSS style-sheet
with the following rule:
.fig--title-label-number {
display: inline;
}
Then add your custom style-sheet in the 'args.css' parameter in the
transformation dialog or define a new publishing template.
You can find more details in our user-guide
.
Regards,
Julien
On 06/08/2021 15:21, Yves Barbion wrote:
> Hi Ionela
>
> Aha! Yes, setting "args.figurelink.style" to NUMBER or NUMTITLE solved
> the problem. The xrefs to the fig now display "Figure 1", "Figure 2" etc.
>
> The figures themselves, however, are not numbered yet. So when I have
> multiple figs on one page, they all just have the label "Figure:" and
> no number in my Oxygen responsive webhelp output. In the HTML5 output
> however, the figures are numbered. Any idea how I can number my
> figures in my webhelp just like in the HTML5?
> Sorry, but my knowledge of css and xsl is rather limited.
> Thank you very much.
>
> Yves
>
> On Fri, 6 Aug 2021 at 12:11, Oxygen XML Editor Support (Ionela
> Istodor) > wrote:
>
> Hi Yves,
>
> To get the same result also for the WebHelp Responsive output you
> need to set 'args.figurelink.style' parameter to 'NUMTITLE'.
> This can be set either in the WebHelp Responsive transformation
> scenario (Parameters tab) or in the Publishing Template descriptor
> file (*.opt).
>
> Regards,
> Ionela
>
> --
> Ionela Istodor
> oXygen XML Editor and Author Support
>
> Tel: +1-650-352-1250 ext.3010
> Fax: +40-251-461482
> support at oxygenxml.com
> http://www.oxygenxml.com
>
>
> ---------------------------------------------------------------------------
> This message (including any attachments) contains confidential information and is intended only for the individual(s) named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Any quotation contained herein has a validity of 30 days, unless otherwise specified. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
>
> On 8/5/2021 10:46 AM, Yves Barbion wrote:
>> Hi group
>>
>> I've got this topic:
>>
>>
>>
>>
>> test
>>
>> See
>>
>>
>>
>>
>>
>>
>> When I generate HTML5 output (using OxygenXML Editor version
>> 23.1), all is well: I see "See Figure 1". When I generate the
>> default responsive output, however, I see the ID of the fig
>> displayed, so "See #test/fig_nmn_q1s_mqb".
>>
>> Any idea how this can be fixed?
>>
>> Thanks
>>
>> Yves
>>
>> _______________________________________________
>> oXygen-user mailing list
>> oXygen-user at oxygenxml.com
>> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
>
>
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From costello at mitre.org Wed Aug 18 09:28:24 2021
From: costello at mitre.org (Roger L Costello)
Date: Wed, 18 Aug 2021 14:28:24 +0000
Subject: [oXygen-user] Why can't Oxygen format and indent a 200MB file in 30
minutes whereas SAXON can do it in 15 seconds?
Message-ID:
Hi Folks,
I have (by today's standards) a medium sized XML file that is 200MB in size. It is unformatted (no indentation). I opened the file in Oxygen and clicked on the format and indent button. After 30 minutes of processing Oxygen gave up with an error message. So I wrote a simple 1-line XSLT program (below) to do the indentation, it took about 15 seconds and was done. Why is it that Oxygen can't indent the file in 30 minutes whereas an XSLT processor (Saxon) can do it in 15 seconds? /Roger
From support at oxygenxml.com Thu Aug 19 09:11:45 2021
From: support at oxygenxml.com (Oxygen XML Editor Support (Adrian Buza))
Date: Thu, 19 Aug 2021 17:11:45 +0300
Subject: [oXygen-user] Why can't Oxygen format and indent a 200MB file
in 30 minutes whereas SAXON can do it in 15 seconds?
In-Reply-To:
References:
Message-ID:
Hello,
Like the saying goes, it depends...
> I opened the file in Oxygen and clicked on the format and indent
> button. After 30 minutes of processing Oxygen gave up with an error
> message.
You haven't mentioned what the error message was, but I'm pretty sure
Oxygen ran out of memory. Basically it ran out of memory in the first
few seconds of formatting then the Java VM struggled to admit this fact
for the rest of the 30 minutes.
So, first it depends on how much memory Oxygen had available (Help >
About, JVM Memory ... Total).
To keep a long story short, if you want Oxygen to format and indent a
large file as fast as Saxon and not risk running out of memory in the
process, it should to do this either without opening the document or at
document opening time.
A. Without opening the document
Use Tools > "Format and Indent Files" or right click on the document in
the Project view and "Format and Indent Files".
B. At document opening time
1. Set Options > Preferences > Editor / Format, [x] "Format and indent
the document on open".
2. Close the document.
3. Reopen the document (File > Reopen last closed editor / Ctrl+Alt+T)
4. Eventually clear the box for [ ] "Format and indent the document on
open" because it will apply to all opened documents.
Read on for the juicy details...
It is actually a huge difference between how Oxygen (an IDE) and Saxon
(a CLI tool) achieve this and what their requirements are for this, even
though the result may be the same.
I can't really speak for Saxon's inner workings, but it might not even
build an XML model into memory depending on Saxon optimizations and if
Saxon streaming is used.
In theory, if you use an input stream that reads and parses the XML one
chunk at a time, and an output stream that writes the XML model as the
first one reads, you don't actually have to load the entire thing into
memory for the purpose of formatting it.
Using Saxon streaming would probably be faster than your result and
could work for a file of any size, but I digress.
By Oxygen's standards 200MB is a large file (> 30MB). That means some
optimizations are enforced to accommodate a file of this size. [1]
For 300MB or more, Oxygen has a "huge files" mode that no longer loads
the entire document in memory and has some more severe limitations. [2]
So this is closer to Oxygen's "huge" limit rather than the "large" limit.
Because Oxygen is an IDE, it loads the document in memory as text (with
the exceptions/optimizations mentioned above) and then builds various
specialized models from the document so that you have all those editing
helpers (Outline, Attributes, Model) or a much more complex model if you
switch to Author mode.
When you format the document while already opened in Text mode, Oxygen
parses the XML and serializes it with the configured formatting options.
Due to the way the model of a text editor is updated, it is not feasible
to make this into a stream and repeatedly update parts of the file (e.g.
line by line), so the entire document contents is replaced when the
formatting ends. This causes a duplication of the entire document in
memory. Oxygen also provides Undo for that formatting in case you don't
like it or have triggered it accidentally, so it also has to keep the
old document. All of this comes at a high price with regard to memory.
Which is what Oxygen usually stumbles upon (running out of memory) when
working with large files.
So, as much as we would want to make it work with large files, it's just
that the amount of memory required to achieve this within an IDE is a
number of times larger than Saxon's (assuming Saxon would actually build
the entire XML model of that document). The solution is to try and
serialize to disk some of the pieces of the puzzle in order to free
memory. This is actually what some of the large/huge mode optimizations
do, but with limited success.
Regards,
Adrian
[1]
https://www.oxygenxml.com/doc/versions/23.1/ug-editor/topics/large-file-editor.html
[2]
https://www.oxygenxml.com/doc/versions/23.1/ug-editor/topics/huge-file-editor.html
Adrian Buza
oXygen XML Editor and Author Support
On 18.08.2021 17:28, Roger L Costello wrote:
> Hi Folks,
>
> I have (by today's standards) a medium sized XML file that is 200MB in size. It is unformatted (no indentation). I opened the file in Oxygen and clicked on the format and indent button. After 30 minutes of processing Oxygen gave up with an error message. So I wrote a simple 1-line XSLT program (below) to do the indentation, it took about 15 seconds and was done. Why is it that Oxygen can't indent the file in 30 minutes whereas an XSLT processor (Saxon) can do it in 15 seconds? /Roger
>
> xmlns:xs="http://www.w3.org/2001/XMLSchema"
> exclude-result-prefixes="xs"
> version="2.0">
>
>
>
>
>
>
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
From support at oxygenxml.com Mon Aug 30 08:34:41 2021
From: support at oxygenxml.com (Oxygen XML Editor Support (Adrian Buza))
Date: Mon, 30 Aug 2021 16:34:41 +0300
Subject: [oXygen-user] [Ann] New maintenance build available for oXygen 23.1
(2021082307)
Message-ID: <9dc92962-3b38-7d43-b961-33edce4fb85e@oxygenxml.com>
Dear oXygen users,
We announce the release of a new maintenance build (2021082307) for
oXygen 23.1 (XML Editor, XML Developer, XML Author, XML WebHelp, PDF
Chemistry, Publishing Engine).
The build number can be verified in the Help -> About dialog box from
the application (next to the version number).
You can download the new installation kits from our web site:
http://www.oxygenxml.com/download.html
Here you can find the complete list of bug-fixes:
http://www.oxygenxml.com/build_history.html#2021082307
You can follow our oXygen release/build RSS feed here:
http://www.oxygenxml.com/rssBuildID.xml
Please let us know if you encounter any problems with this new build.
Regards,
Adrian
--
Adrian Buza
oXygen XML Editor and Author Support
From lou.burnard at retired.ox.ac.uk Tue Aug 31 06:37:56 2021
From: lou.burnard at retired.ox.ac.uk (Lou Burnard)
Date: Tue, 31 Aug 2021 12:37:56 +0100
Subject: [oXygen-user] cant run spell check on my raspberry
Message-ID:
I have been having fun running oXygen (v 23.1) on my little Raspberry
400. It takes a while to load from the USB stick, but runs smoothly
(despite dire warnings at startup). However, I have hit a problem trying
to use the spell checker, since you (obviously) don't ship a Raspbian
binary of hunspell. The popup says "Error: could not load Hunspell. The
error message was: Unknown OS/arch: linux/arm"
Now, back in 2012, when someone reported the exact same problem here
(but with reference to Solaris), they were advised to set the "spell
checking engine" to "Java spell checker", which looked promising.
However, that option is no longer available so far as I can tell,
certainly not where Adrian said it was!
Any suggestions?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From support at oxygenxml.com Tue Aug 31 08:10:48 2021
From: support at oxygenxml.com (Oxygen XML Editor Support (Adrian Buza))
Date: Tue, 31 Aug 2021 16:10:48 +0300
Subject: [oXygen-user] cant run spell check on my raspberry
In-Reply-To:
References:
Message-ID:
Hello,
I'm afraid that the "Java spell checker" is no longer an option in
recent versions of Oxygen. It has been removed since v19.1.
The Hunspell spellchecker is a native implementation, so it requires a
Hunspell binary that is compiled for your platform.
Unfortunately the Hunspell library loader from Oxygen does not provide
the means to load a library for an unknown (unsupported) architecture,
so even if you compile the Hunspell source code for linux/arm, it's not
possible to convince Oxygen to load it.
Regards,
Adrian
Adrian Buza
oXygen XML Editor and Author Support
On 31.08.2021 14:37, Lou Burnard wrote:
>
> I have been having fun running oXygen (v 23.1) on my little Raspberry
> 400. It takes a while to load from the USB stick, but runs smoothly
> (despite dire warnings at startup). However, I have hit a problem
> trying to use the spell checker, since you (obviously) don't ship a
> Raspbian binary of hunspell. The popup says "Error: could not load
> Hunspell. The error message was: Unknown OS/arch: linux/arm"
>
> Now, back in 2012, when someone reported the exact same problem here
> (but with reference to Solaris), they were advised to set the "spell
> checking engine" to "Java spell checker", which looked promising.
> However, that option is no longer available so far as I can tell,
> certainly not where Adrian said it was!
>
> Any suggestions?
>
>
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: