Re: [Ann] Oxygen XML Editor version 23 release

>  By the way, Geert, I don't think MSXML supports debugging, at least in
my Oxygen version it switches to Saxon when I try that.

Visual Studio has had an XSLT Debugger since VS 2008. I think it is based
on the .NET XSLTransform, but the behavior of the two XSLT processors is
almost identical (both are almost 100% compliant to the official XSLT 1.0
and XPath 1.0 specification). The debugger has even such advanced features
as "data breakpoints".

Thanks,
Dimitre

On Mon, Nov 23, 2020 at 7:43 AM Willem Van Lishout
[email protected] <[email protected]> wrote:

> I have to agree with the others. XSLT 1.0 is unfortunately still very
> prevalent, and I sometimes need to use MSXML to see what quirks it
> produces. (There's quite a few of them!)
>
> If you are really keen on removing them, I would at least consider making
> them available as easily installable plugins.
>
> By the way, Geert, I don't think MSXML supports debugging, at least in my
> Oxygen version it switches to Saxon when I try that.
> On Nov 23, 2020, at 15:26, "Geert Bormans [email protected]" <
> [email protected]> wrote:
>>
>> Hi Octavian,
>>
>> Thanks for the update
>>
>> As much as I don't like it...
>> some customers can not or don't want to migrate to an XSLT version higher
>> than 1.0,
>> and I am not always in a position to change that (and that will continue
>> to be so for a long while I am afraid)
>> So I guess I will be needing debugging support for at least Xalan and
>> msxml 4.0 or .net for some time to come,
>> it is what it is :-(
>>
>> configuring them as external processors, does not give me real debugging
>> support, does it
>>
>> Met vriendelijke groeten,
>> Best regards,
>>
>> Geert Bormans
>>
>> ----- Op 23 nov 2020 om 14:47 schreef Octavian Nadolu
>> [email protected] <[email protected]>:
>>
>> Hello,
>>
>> Thanks for your feedback.
>>
>> We intend to update the Saxon 9 and 10 plugins for the Oxygen XML Editor
>> 23.0. Because this are provided separately as plugins, we can updated them
>> also after the release.
>>
>> We decided to deprecate some of the XSLT processors (Xalan, MSXML 4.0,
>> MSXML .NET, .NET 1.0, .NET 2.0 ...) because we do not want to maintain them
>> in the future. We are not sure if we will remove them completely or just
>> mark them as deprecated. But we will maintain the XSLT 1.0 support in
>> Oxygen. Also, you can configure them as external processors.
>> How many of you are using this processors?
>>
>> Best Regards,
>> Octavian
>>
>> On 23.11.2020 10:46, Mukul Gandhi [email protected] wrote:
>>
>> On Sun, Nov 22, 2020 at 12:44 PM Mukul Gandhi [email protected] <
>> [email protected]> wrote:
>>
>>> I can see that, at the preferences oXygen page, XSLT 1.0 dropdown shows
>>> Xalan as deprecated. It seems to me that, in a future oXygen version, when
>>> Xalan would be removed from the standard oXygen XSLT 1.0 options, one could
>>> still use Xalan with oXygen by specifying it on the 'Custom Engines'
>>> option.
>>>
>>
>> Apologies, that I forgot to mention that, I tried oXygen XML Editor
>> version 23.
>>
>>
>>
>> --
>> Regards,
>> Mukul Gandhi
>> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
>> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/1205338> ( by
>> email)
>>
>>
>> --
>> Octavian Nadolu
>> <oXygen/> XML Editorhttp://www.oxygenxml.com
>>
>> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
>> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/554170> ( by
>> email)
>>
>> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
>> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/3166594> ( by
>> email)
>>
> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/782854> (by
> email <>)
>
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/3329386
or by email: [email protected]
--~--