EDIT: this should be the XHTML 1.1 Modularization implementation.

http://www.w3.org/TR/xhtml11/xhtml11_sc ... 1s_modules

thanks Radu. This works fine. As per XHTML Modularization, it seems that this is just a XHTML Basic example. I'm really interested in extending XHTML Transictional but I didn't find such implementation. I'm just figure out if someone else did it or there is a working example. Anyway I'll try to crea...

Sorry for append question to an old post, but I'm figure out if a solution was found for the error: E [Xerces] derivation-ok-restriction.2.1.2: Error for type 'xhtml.version.attrib'. The attribute use 'version' in this type has type 'FPI', which is not validly derived from 'CDATA', the type of the m...

Done! It works fine

Thanks Sorin, and sorry for last trivial question... sometimes I forgot the manual

thanks Sorin for your replay, that confirmed my suspects :-) Well, supposing I would like to run such java class as a different xslt engine (say, CustomSaxon) inside the Oxygen IDE: is it possible to do? Can I configure a scenario that works with my CustomSaxon? And what parameter I must manage insi...

Hi Jason, it seems that a fo:footnote is not correct placed.

I suggest to apply your transformation scenario just converting your xml to xsl-fo (whitout rendering to pdf) then open the fo file in oxygen and check where is the error.

I have found what I'm missing and put it the answer for other people that could have similar question. Simply, the FO spec don't address a "block vertical justification". That's all. To obtain such results, a double pass technique is required in order to check the resulting height by fop a...

Hi all. I'm working on a custom extension in order to provide some functions to XSLT by Saxon. My firs approach was to test Saxon EE provided by Oxigen itself: I created a simple java class, put it in a jar and place this jar in <oxigenx install dir>/lib. Then declaring a namespace such xmlns:see=&q...

I'm not sure this is the right place for this question (it seems more related to FO, but not sure). Anyway: This block-progression-dimension is driving me crazy. Probably I didn't understood how it works... well, this is the problem: I must create a table with 3 rows and 2 columns. The width of 2 co...

tks adrian. I'll check it!

Thanks adrian.

I already did some changes on fo.xsd available in Oxygen to take in account some custom tags (say, fop custom extension). What I try to do is work both with xslt (and fo) 1.0 and 1.1 depending on project requirements.

Probably is it possible to add a new custom namespace to do this?

I have a question about FO version and fo:wrapper element. As per xslt 1.0 the fo:wrapper element allows only the id attribute: http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo_wrapper but as per xslt 1.1 the common properties index-class and index-key are added: http://www.w3.org/TR/xsl/#f...

I solved this problem in FOP adopting a dedicated small cap font variant, say Times New Roman Small Cap and declaring a configuration xml file for FOP to embed the font in PDF output.

Great!

Thank you

Thanks Radu. I will do it.

I will keep a backup copy of the original fo.xsd.

By the way, do you think that there is a config file to say to oxygen wich xsd must be used for grammar checking?

Hi all, I'm working with Oxygen 11.1 and I was able a external FO processor based on the built-in FOP libraries and the extension library in order to manage FOP Extension such fox:external-document and so on. The problem is that in the editor page the FO validation is not passed due to the fox:exter...