headers
Radu Coravu | 5 Aug 2010 10:13
Picon
Favicon
Gravatar

Re: mystery: content-height validation problem with XEP

Hi Robert,

For example if in a Docbook 5 XML file you have an image like:

<imagedata fileref="../lake.jpeg" scale="100" contentdepth="50"/>

in the generated FO file (which gets transformed to PDF) it gets 
transformed to:

<fo:external-graphic src="url(../lake.jpeg)" width="auto"
                             height="auto" content-width="auto" 
content-height="50px"/>

I tested with both Apache FOP and XEP 4.16 and they both accept the 
content-height with the value specified with "px" (and without the px 
appended as well).
Maybe you are using an older version of XEP?

Regards,
Radu

--

-- 
Radu Coravu
<oXygen/>   XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 7/31/2010 11:20 AM, Robert Nagle wrote:
> Hi, I have a weird problem and am flummoxed.
>
> I have oxygen 11.2 + xep + docbook 5.
(Continue reading)

Permalink | Reply | 1 comment |
headers
john.hockaday | 9 Aug 2010 01:11
Picon

Can't access external XML documents [SEC=UNCLASSIFIED]

Hi all,

I have in the past been able to access external XML documents using Schematron external validation. I set my
proxy, username and password in the Options => Preferences. I now can't access the external XML documents
when I validate using Schematron external validation. I get the following error:
"
SystemID: G:\asdd\profileinfo\Camera.xml
Description: [ISO Schematron (XSLT 2.0)] org.apache.commons.httpclient.HttpException: Malformed
reply from SOCKS server (http://asdd.ga.gov.au/asdd/profileinfo/gmxCodelists.xml)
"

The errors in the oxygen.log file looks like this:

"
...
Editor,resizable,maximized,defaultCloseOperation=DO_NOTHING_ON_CLOSE,rootPane=javax.swing.JRootPane[,4,23,1280x1005,invalid,layout=javax.swing.JRootPane$RootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=16777673,maximumSize=,minimumSize=,preferredSize=],rootPaneCheckingEnabled=true]
13990767 DEBUG [ AWT-EventQueue-0 ] ro.sync.ui.application.ApplicationDialog - parent: java.awt.Rectangle[x=1276,y=-4,width=1288,height=1032]
13990767 DEBUG [ AWT-EventQueue-0 ] ro.sync.ui.application.ApplicationDialog - parentDedDevice:
12282778 Bounds: java.awt.Rectangle[x=1280,y=0,width=1280,height=1024]
13990767 DEBUG [ AWT-EventQueue-0 ] ro.sync.ui.application.ApplicationDialog - bestFitDevice:
12282778 Bounds: java.awt.Rectangle[x=1280,y=0,width=1280,height=1024]
14022947 DEBUG [ AWT-EventQueue-0 ] ro.sync.ui.application.ApplicationDialog - The focused window
is: 
ro.sync.ui.application.ApplicationDialog$_B[dialog2,1615,423,610x177,invalid,layout=java.awt.BorderLayout,APPLICATION_MODAL,title=Validate with,defaultCloseOperation=DO_NOTHING_ON_CLOSE,rootPane=ro.sync.ui.application.ApplicationDialog$2[,4,23,602x150,layout=javax.swing.JRootPane$RootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=],rootPaneCheckingEnabled=true]
14022947 DEBUG [ AWT-EventQueue-0 ] ro.sync.ui.application.ApplicationDialog - KFM:
ro.sync.ui.application.ApplicationDialog$_B[dialog2,1615,423,610x177,invalid,layout=java.awt.BorderLayout,APPLICATION_MODAL,title=Validate with,defaultCloseOperation=DO_NOTHING_ON_CLOSE,rootPane=ro.sync.ui.application.ApplicationDialog$2[,4,23,602x150,layout=javax.swing.JRootPane$RootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=],rootPaneCheckingEnabled=true]
14022947 DEBUG [ AWT-EventQueue-0 ] ro.sync.ui.application.ApplicationDialog - The top window:
ro.sync.ui.application.ApplicationDialog$_B[dialog2,1615,423,610x177,invalid,layout=java.awt.BorderLayout,APPLICATION_MODAL,title=Validate with,defaultCloseOperation=DO_NOTHING_ON_CLOSE,rootPane=ro.sync.ui.application.ApplicationDialog$2[,4,23,602x150,layout=javax.swing.JRootPane$RootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=],rootPaneCheckingEnabled=true]
14200437 INFO [ External Validator ] org.apache.commons.httpclient.HttpMethodDirector - I/O
exception (java.net.SocketException) caught when processing request: Malformed reply from SOCKS server
(Continue reading)

Permalink | Reply | 7 comments |
headers
Radu Coravu | 9 Aug 2010 09:02
Picon
Favicon
Gravatar

Re: Can't access external XML documents [SEC=UNCLASSIFIED]

Hi John,

Did you by any change set up a SOCKS Proxy in the "HTTP(S)/(S)FTP/Proxy 
Configuration" Oxygen preferences page?
Is it necessary to you or was it set accidentally?
Because the error seems to indicate that a SOCKS Proxy was set up and it 
responded with an invalid response to the client.
You can also find more details about the HTTP connection by adding this 
line to the "log4j.properties" file:

log4j.category.httpclient.wire=debug

If you have a SOCKS proxy server configured, was it recently updated? 
Oxygen is a Java program and the Java Virtual Machine seems only to 
support Socks v4.
See this post:
http://www.innovation.ch/java/HTTPClient/errors.html

Regards,
Radu

--

-- 
Radu Coravu
<oXygen/>   XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 8/9/2010 2:11 AM, john.hockaday@... wrote:
> Hi all,
>
> I have in the past been able to access external XML documents using Schematron external validation. I set
(Continue reading)

Permalink | Reply | 6 comments |
headers
john.hockaday | 10 Aug 2010 02:01
Picon

Re: Can't access external XML documents [SEC=UNCLASSIFIED]

Ah-ha! Radu. That was it. ;--)

Thank you very much.

John

> -----Original Message-----
> From: Radu Coravu [mailto:radu_coravu@...]
> Sent: Monday, 9 August 2010 5:02 PM
> To: oXygen User ML
> Subject: Re: [oXygen-user] Can't access external XML
> documents [SEC=UNCLASSIFIED]
>
> Hi John,
>
> Did you by any change set up a SOCKS Proxy in the
> "HTTP(S)/(S)FTP/Proxy
> Configuration" Oxygen preferences page?
> Is it necessary to you or was it set accidentaAhally?
> Because the error seems to indicate that a SOCKS Proxy was
> set up and it
> responded with an invalid response to the client.
> You can also find more details about the HTTP connection by
> adding this
> line to the "log4j.properties" file:
>
> log4j.category.httpclient.wire=debug
>
> If you have a SOCKS proxy server configured, was it recently updated?
> Oxygen is a Java program and the Java Virtual Machine seems only to
(Continue reading)

Permalink | Reply | 0 comments |
headers
George Cristian Bina | 12 Aug 2010 11:45
Favicon
Gravatar

Cast your vote for the next oXygen splash screen

You can choose from 3 proposals the one you like at:
http://www.oxygenxml.com/forum/topic5203.html

Thanks,
George
--

-- 
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
Permalink | Reply | 1 comment |
headers
Wendell Piez | 12 Aug 2010 17:51
Favicon

Re: mystery: content-height validation problem with XEP

Hi,

I know this is old, but just a wild guess -- if the stylesheet 
expects a value and doesn't find one, the FO could be coming out

<fo:external-graphic ... content-height="px"/>

and I wouldn't be surprised to see XEP complain about that.

Cheers,
Wendell

At 04:13 AM 8/5/2010, Radu wrote:
>Hi Robert,
>
>For example if in a Docbook 5 XML file you have an image like:
>
><imagedata fileref="../lake.jpeg" scale="100" contentdepth="50"/>
>
>in the generated FO file (which gets transformed to PDF) it gets
>transformed to:
>
><fo:external-graphic src="url(../lake.jpeg)" width="auto"
>                              height="auto" content-width="auto"
>content-height="50px"/>
>
>
>I tested with both Apache FOP and XEP 4.16 and they both accept the
>content-height with the value specified with "px" (and without the px
>appended as well).
(Continue reading)

Permalink | Reply | 0 comments |
headers
Florent Georges | 12 Aug 2010 21:30

Empty the Calabash's cache

  Hi,

  The source port of an XProc pipeline is connected to a file on
the file system:

    <p:input port="source">
       <p:document href="input.xml"/>
    </p:input>

  I run the pipeline with the built-in scenario "Self XProc, no
input no output".  If I modify input.xml and run the piepline
again, the changes are not picked up.

  A feature of Calabash is to cache all inputs in memory (I
think).  So I guess the same processor is kept in memory by
oXygen, but I think oXygen should empty the Calabash's cache
between two runs of the pipeline (or get rid of the processor and
instantiate it again if this is not possible).

  Besides, this pipeline loops over a lot of files, so that means
they are kept in memory "for ever" (as long as oXygen itself is
alive).

  Regards,

--

-- 
Florent Georges
http://fgeorges.org/
Permalink | Reply | 1 comment |
headers
Florent Georges | 12 Aug 2010 21:31

Schema translator tool: from XSD to *

Hi,

  Is there any reason why the oXygen's schema translator tool
does not support translation from an XSD schema?  I used to use
rngconv from the command line, but it would be nice to have it
integrated within oXygen.

  But maybe that's because of a licence issue, I don't know.

  Regards,

--
Florent Georges
http://fgeorges.org/
Permalink | Reply | 2 comments |
headers
George Cristian Bina | 13 Aug 2010 10:57
Favicon
Gravatar

Re: Schema translator tool: from XSD to *

Hi Florent,

The schema conversion support is based on Trang and Trang does not 
support XSD as input.
As far as I remember there was indeed a licensing issue related with Sun 
MSV/rngconv. Now, looking again it seems that all are BSD although the 
rngconv package contains also a copyright.txt file containing

...
Sun Microsystems, Inc. has intellectual property rights relating to
technology embodied in this product. In particular, and without
limitation, these intellectual property rights may include one or more
of the U.S. patents listed at http://www.sun.com/patents and one or
more additional patents or pending patent applications in the U.S. and
other countries. This product is distributed under licenses
restricting its use, copying, distribution, and decompilation. No part
of this product may be reproduced in any form by any means without
prior written authorization of Sun and its licensors, if any. Third
party software, including font technology, is copyrighted and licensed
from Sun suppliers.
...

Searching on MSV/rngconv shows that they were licensed under Apache 
Software License and Sun Binary Software License Agreement, see
http://www.xml.com/pub/r/1265

We will look more into these to see if it possible to distribute that 
with oXygen.

Best Regards,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Florent Georges | 13 Aug 2010 11:22

Re: Schema translator tool: from XSD to *

George Cristian Bina wrote:

> We will look more into these to see if it possible to distribute
> that with oXygen.

  Good news, thanks for looking into this!

  Regards,

--

-- 
Florent Georges
http://fgeorges.org/
Permalink | Reply | 0 comments |

Gmane