Thanks so much for the help. The issue was due to my attempt to use
ArialUnicodeMS as the font.
-Ray
On Wed, May 28, 2014 at 9:48 PM, Glenn Adams wrote:
> You do not need to specify the script property, unless the automatic
> algorithm doesn't select the desired script. This latter would only be the
> case if you are using an older font that supports only the pre-2005
> OpenType Devanagari rendering rules ('deva'). The current automatic
> algorithm maps to 'dev2', which matches the current OpenType font spec.
>
>
> On Thu, May 29, 2014 at 3:55 AM, Raymond Budd wrote:
>
>> Hi,
>>
>> I have a question about Devanagari support. Please excuse my limited
>> background with the script.
>>
>> The site shows that join controls are not supported:
>> https://xmlgraphics.apache.org/fop/trunk/complexscripts.html, and I want
>> to make sure the behavior I see is as expected. A basic example of this is
>> with: में
>>
>> On command line PDF generation with the example FO file below, this
>> generates two separate characters instead of the single character above (I
>> can provide the config, FO, and generated PDF files if it helps). I get the
>> same result when running with script set to 'dev2' or 'deva'.
>>
>> If this is currently not supported, does anyone have an idea of when this
>> support would be available, if there's a workaround, or suggestion for
>> improving the results?
>>
>> Also, I'm not sure I understand the distinction between the standard and
>> extended script codes. Is there a pointer to somewhere I can find out more
>> about the difference?
>>
>> Thanks in advance for any help,
>> Ray
>>
>>
>> sample FO file:
>>
>>
>>
>> http://www.w3.org/1999/XSL/Format";
>> font-family="Arial">
>>
>> > margin-left="54pt" margin-right="54pt" page-width="8.5in"
>> page-height="11in" master-name="normal">
>>
>>
>>
>>
>>
>> > script="deva" font-family="ArialUnicodeMS" font-size="14pt">
>> में
>>
>>
>>
>>
>>
>>
>>
>
