[xep-support] Intermediate format question

[Teus Benschop]

Thank you a lot for this solution. From what you say it seems this is 
going to work. Because what our intermediate processor needs is just 
some text, and this pinpoint extension gives it. It actually is better 
because the _elastic_ will under no circumstances be put into the pdf file.

Thanks,

Teus.

Geoff Levner wrote:
> Ah, right.  Then perhaps you can use RenderX's pinpoint extension.  If 
> you insert an element like this inside the fo:block in your XSL-FO 
> file, or before it:
>
>    <rx:pinpoint value="_elastic_"/>
>
> Then you will see something this in your XEP intermediate file:
>
>    <xep:pinpoint value="_elastic_"/>
>
> Note that to use RenderX extensions you will need to declare the "rx" 
> namespace in your stylesheet:
>
>    <xsl:stylesheet version="1.0"
>       xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>       xmlns:rx="http://www.renderx.com/XSL/Extensions"
>       ...>
>
> Note also that pinpoints are a little bit capricious.  Depending on 
> where you put them in your XSL-FO, they do not always appear exactly 
> where you would expect them in the XEP file...
>
> Geoff
>
>
> On 3 Oct 2006, at 10:23, Teus Benschop wrote:
>
>> Thanks for the suggestion. But as far as I am aware the attribute 
>> does not get transferred to the intermediate XEP format file. That 
>> file only contains the actual text that goes into the pdf file.
>>
>> Regards,
>>
>> Teus.
>>
>> Geoff Levner wrote:
>>> It would be simpler to put "_elastic_" into an attribute of your 
>>> fo:block, wouldn't it?  Then you would not have to worry about XEP 
>>> processing it.  You might use the "id" attribute, for example.
>>>
>>> Geoff
>>>
>>> On 3 Oct 2006, at 07:36, Teus Benschop wrote:
>>>
>>>> Hi,
>>>>
>>>> We've a minor problem here with the XEP intermediate format, and 
>>>> perhaps somebody knows a solution for it.
>>>>
>>>> Our scenario is this.
>>>> We've a text.fo xslfo file, convert that text.fo to XEP 
>>>> intermediate format, using the "-format xep" switch, then we 
>>>> process that text.fo.xep intermediate file, and then produce a pdf 
>>>> out of it.
>>>>
>>>> The text.fo file has the word "_elastic_" in it, like so:
>>>>
>>>> <fo:block font-size="12pt" text-align="left" space-before="0mm" 
>>>> space-after="0mm" start-indent="0mm" end-indent="0mm" 
>>>> text-indent="0mm" span="all" intrusion-displace="line" widows="2" 
>>>> orphans="2">
>>>> _elastic_
>>>> </fo:block>
>>>>
>>>> The word "_elastic_" triggers our processor and cause it do take 
>>>> some actions.
>>>>
>>>> Depending on the font chosen, at times the word "_elastic_" gets 
>>>> into the text.fo.xep intermediate file as one whole word, but 
>>>> sometimes it gets divided into two bits, like so:
>>>>
>>>> <xep:text value="_elas" x="56693" y="774889" width="24528"/>
>>>> <xep:text value="tic_" x="81221" y="774889" width="18000"/>
>>>>
>>>> If the words is available as one whole word, our processor finds 
>>>> it, and handles it properly, but if the processor finds "_elas" and 
>>>> then "tic_" later, it does not recognize this as a special word to 
>>>> be handled, does not get triggered, and therefore does nothing, and 
>>>> the "_elastic" appears in the output pdf, which is undesired.
>>>>
>>>> My question is whether there are any instructions to be given to 
>>>> XEP to put some text as one unit into the intermediate file, like so:
>>>>
>>>> <xep:text value="_elastic_" x="56693" y="774889" width="42528"/>
>>>>
>>>> Thanks for any help,
>>>>
>>>> Regards,
>>>>
>>>> Teus Benschop
>>>> Free Presbyterian Church
>>>
>>> -------------------
>>> (*) To unsubscribe, send a message with words 'unsubscribe xep-support'
>>> in the body of the message to majordomo at renderx.com from the address
>>> you are subscribed from.
>>> (*) By using the Service, you expressly agree to these Terms of 
>>> Service http://www.renderx.com/terms-of-service.html
>>>
>>>
>> -------------------
>> (*) To unsubscribe, send a message with words 'unsubscribe xep-support'
>> in the body of the message to majordomo at renderx.com from the address
>> you are subscribed from.
>> (*) By using the Service, you expressly agree to these Terms of 
>> Service http://www.renderx.com/terms-of-service.html
>>
>
> -------------------
> (*) To unsubscribe, send a message with words 'unsubscribe xep-support'
> in the body of the message to majordomo at renderx.com from the address
> you are subscribed from.
> (*) By using the Service, you expressly agree to these Terms of 
> Service http://www.renderx.com/terms-of-service.html
>
>
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo at renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html