[xep-support] how do i make writing mode property work?

[Rajat Vig]

Hi Alexander,

Thanks for the help. The writing mode worked.
I set it on the flow objects.

But still I don't see Hebrew text.
It's not coming garbled but it's coming empty, i.e., any text I write as
Hebrew it just doesn't come.
I am using the Times/serif font. I've attached the FO file.

There is yet another problem that has come up once I changed the writing
mode.
One of the tables in the static contents is not being drawn.
I tried rendering the same document through FOP and it shows me the table.
The table I'm referring to is the headings of the columns drawn in the body.

As for the transformation, I'll give it a try again for now I'm transforming
with Xalan myslef and calling XEP via a script for the FO.
I tried the JAXPDriver only and it complained about needing Saxon (I had
Xalan in my classpath) and Saxon complained my style sheet was incorrect.

I've a trial version of XEP. Could any of my problems be because of that?

Thanks,
Rajat Vig
E-mail: rajat.vig at amdocs.com
Phone (off): +357-25-845779
Phone (mobile): +357-99-822460

In the construction of Immortal Fame you need first of all a cosmic
shamelessness.
-- "Travels in Hyperreality" (1975) from Travels in Hyperreality

-----Original Message-----
From: Alexander Peshkov [mailto:peshkov at renderx.com]
Sent: Wednesday, November 06, 2002 4:18 PM
To: Rajat Vig
Subject: Re: [xep-support] how do i make writing mode property work?


Hello Rajat,

RV> Hi All,

RV> I've set the writing-mode to "rl-tb" in the simple page master but it
has
RV> absolutely no effect on the layout of the page.
RV> I typed some Hebrew text in the FO document and it comes up garbled in
the
RV> output PDF.
RV> I've attached the FO file I'm using.

You should specify writing-mode on fo:block-container to make it work.
If you want to apply writing-mode to the whole flow, you should wrap it in
block-container.
What do you mean by "garbled" then talking about Hebrew text? Do you
have appropriate font-family specified? (the one which contains Hebrew
glyphs).

RV> There are some more issues I have with XEP with regards to XML/XSL
RV> transformations...
RV> If I pass the XML and XSL separately to XEP, it complains of errors in
my
RV> style sheet but FOP processes it.
RV> The XSL is valid as Xalan correctly transforms the XML to FO using the
same
RV> XSL.

May I ask you in which way you pass XSL FO and stylesheet to XEP?
The right way to do it from command-line is to use JAXPDriver.

RV> Any ideas why should it be so? Also, can I change the Transformer XEP
uses?
RV> Why does XEP require Saxon and XT both if I'm passing it only the FO
RV> document?

JAXPDriver can use any JAXP-compatible transformer available in your
system. It could be explicitly specified via
javax.xml.transform.TransformerFactory system property.

As for XT - XEP uses it for internal processing.

Best regards,
Alexander Peshkov                             mailto:peshkov at renderx.com
RenderX


RV> Thanks,
RV> Rajat Vig
RV> E-mail: rajat.vig at amdocs.com
RV> Phone (off): +357-25-845779
RV> Phone (mobile): +357-99-822460

RV> And yet, and yet . . . Denying temporal succession, denying the self,
RV> denying the astronomical universe, are apparent desperations and secret
RV> consolations. Our destiny is not frightful by being unreal; it is
frightful
RV> because it is irreversible and iron-clad. Time is the substance I am
made
RV> of. Time is a river which sweeps me along, but I am the river; it is a
tiger
RV> which destroys me, but I am the tiger; it is a fire which consumes me,
but I
RV> am the fire. The world, unfortunately, is real; I, unfortunately, am
Borges.
RV> -- Essay: "A New Refutation of Time," 1946


-------------------
By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/tos.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: InvoiceReportTotalReport.fo
Type: application/octet-stream
Size: 16743 bytes
Desc: not available
URL: <http://lists.renderx.com/pipermail/xep-support/attachments/20021107/3bdeb2a6/attachment.obj>
-------------- next part --------------
-------------------------------------------------------------------------------------

The information contained in this message is proprietary of Amdocs,

protected from disclosure, and may be privileged.

The information is intended to be conveyed only to the designated recipient(s)

of the message. If the reader of this message is not the intended recipient,

you are hereby notified that any dissemination, use, distribution or copying of 

this communication is strictly prohibited and may be unlawful. 

If you have received this communication in error, please notify us immediately

by replying to the message and deleting it from your computer.

Thank you.


-------------------------------------------------------------------------------------