Re: Error using encoding="utf-8" to output RML to PDF

On 09/06/2017 16:06, Robert Sullivan wrote:
> Hi Robin,
> 
> In preparing the smallest possible example I discovered I don't get the
> error when using Helvetica just with Gotham. So the entities are working
> fine.
> 
> Here is the docinit snippet and we are using utf-16 encoding.
> 
> <docinit>
>          {% if font == "Gotham" %}
>              <registerTTFont faceName="{{ font }}" fileName="{{ asset_root
> }}/{{ font }}-Book.ttf" />
>              <registerTTFont faceName="{{ font }}-Bold" fileName="{{
> asset_root }}/{{ font }}-Bold.ttf" />
>              <registerTTFont faceName="{{ font }}-Italic" fileName="{{
> asset_root }}/{{ font }}-BookItalic.ttf" />
>              <registerTTFont faceName="{{ font }}-Black" fileName="{{
> asset_root }}/{{ font }}-Black.ttf" />
>              <registerFontFamily
>                  normal="Gotham"
>                  bold="Gotham-Bold"
>                  italic="Gotham-Italic"
>                  boldItalic="Gotham-Black" />
>          {% endif %}
>      </docinit>
> 
hi could this just be the use of the font or asset_root interpolations? I don't 
know exactly what django templates are supposed to output in this case. I always 
just use preppy to prepare rml.

Have you actually saved the output that is produced from the template and 
checked it is all in utf-16. I think that means we need unicode as the django 
template output.

There's a bug in the current go method when saveRml='path' is passed in as it 
will try to save the rml with a 'w' mode argument and you'll just get an error 
there.

So you should probably save the produced RML yourself with a 'wb' mode argument.

I think this is almost certainly a problem in the content of the RML rather than 
an issue in the font itself. Missing glyphs should just appear as black squares 
etc etc.


> Also using Python3.6 and Django 1.10.5, fyi, so the font is declared in the
> context variable that gets passed to this template.
> 
> I'll look more into the Gotham font but any pointers would be appreciated.
> 
> Many thanks,
> 
> Robert
> 
> On 8 June 2017 at 12:20, Robin Becker <[email protected]> wrote:
> 
>> Hi Robert,
>>
>> can you email me (attached as a zip) the smallest possible example where
>> this happens? Also what version of python/platform are you using?
>>
>> I have tested by just inserting the &divide; into a simple test rml
>>
>>
>> <!DOCTYPE document SYSTEM "../rml.dtd">
>> <document filename="tdivide.pdf" invariant="1">
>>
>> <stylesheet>
>> <paraStyle
>>          name="intro"
>>          fontName="Helvetica"
>>          fontSize="12"
>>          leading="12"
>>          />
>> </stylesheet>
>>
>> <pageDrawing>
>> <drawCentredString x="4.1in" y="5.8in">
>> Hello World. First Page Drawing &divide;
>> </drawCentredString>
>> </pageDrawing>
>>
>> </document>
>>
>>
>> that works for me with python 2.7 3.3...
>>
>> I suspect you have been more formal and have put in some encodings at the
>> top somehow. The encoding eclared appears to be utf8 and the text of the
>> rml appears to be something other than utf8.
>>
>>
>> On 08/06/2017 11:37, Robert Sullivan wrote:
>>
..........
>> --
>> Robin Becker
>>
> 


-- 
Robin Becker