W3C home > Mailing lists > Public > xproc-dev@w3.org > December 2010

Re: XProc confuses me; recommendations for learning?

From: Romain Deltour <rdeltour@gmail.com>
Date: Mon, 20 Dec 2010 10:30:25 +0100
Cc: XProc Dev <xproc-dev@w3.org>
Message-Id: <96C87B35-E08A-4207-AED4-0933867B433C@gmail.com>
To: George Cristian Bina <george@oxygenxml.com>
Works great. Thanks!

Romain.

Le 20 déc. 10 à 09:58, George Cristian Bina a écrit :

> Hi,
>
> This was already implemented in the current development stream and  
> it will be available in oXygen 12.1.
>
> If you want earlier access to this you can use it from the following  
> beta:
> http://www.oxygenxml.com/update/12.1-beta/oxygen.tar.gz
>
> If you want the 12.0 plus the updated Calabash connector then just  
> expand this archive and replace the [oxygen]/lib/xproc/calabash  
> folder from your oXygen installation with the corresponding folder  
> from the 12.1 beta archive.
>
> Best Regards,
> George
> -- 
> George Cristian Bina
> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
>
> On 12/17/10 10:19 PM, Philip Fennell wrote:
>> Romain wrote:
>>
>>> Btw, Is it just me or the p:log is disabled when running from  
>>> oXygen ?
>>
>> Now  you come to mention it, I think I read something like that  
>> somewhere too.
>>
>>
>> Regards
>>
>> Philip Fennell
>> Consultant
>> MarkLogic Corporation
>>
>>
>>
>> -----Original Message-----
>> From: Romain Deltour [mailto:rdeltour@gmail.com]
>> Sent: 17 December, 2010 7:56 PM
>> To: Philip Fennell
>> Cc: XProc Dev
>> Subject: Re: XProc confuses me; recommendations for learning?
>>
>> Philp Fennell wrote:
>>> The p:log instruction is one possible tool for debugging (...) Note:
>>> in oXygen you need to got to the XML/XProc preferences and select
>>> 'Show XProc Messages' is you want to see cx:message output.
>>
>> Btw, Is it just me or the p:log is disabled when running from  
>> oXygen ?
>> (I know I should ask on oXygen forums, but I came against the issue a
>> few minutes before reading this thread...)
>>
>> Romain.
>>
>> Le 17 déc. 10 à 18:53, Philip Fennell a écrit :
>>
>>> David,
>>>
>>>> is the inability to see what the XProc processor is seeing.
>>>
>>> The p:log instruction is one possible tool for debugging. The other,
>>> if you're using Calabash is the cx:message extension step. The
>>> former writes what appears on a port out to a URI and the latter
>>> writes to stdout. They're both very useful. Note: in oXygen you need
>>> to got to the XML/XProc preferences and select 'Show XProc Messages'
>>> is you want to see cx:message output.
>>>
>>>
>>> Regards
>>>
>>> Philip Fennell
>>> Consultant
>>> MarkLogic Corporation
>>>
>>> -----Original Message-----
>>> From: xproc-dev-request@w3.org [mailto:xproc-dev-request@w3.org] On
>>> Behalf Of David Priest
>>> Sent: 17 December, 2010 5:43 PM
>>> To: xproc-dev@w3.org
>>> Subject: Re: XProc confuses me; recommendations for learning?
>>>
>>> I think the biggest impediment to my understanding is the  
>>> inability to
>>> see what the XProc processor is seeing.  I get error messages about
>>> this
>>> or that not being XML, but no way to actually view the data that has
>>> caused the problem.  With XSLT I can always spit out a message, and
>>> see
>>> the junk data first-hand.
>>>
>>
Received on Monday, 20 December 2010 09:31:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 December 2010 09:31:04 GMT