Re: Embedded font problems
Tim Roberts <[email protected]>
| Newsgroups | gmane.comp.python.reportlab.user |
|---|---|
| Organization | Providenza & Boekelheide, Inc. |
| Message-ID | <[email protected]> |
Robin Becker wrote:
> On 13/03/2017 16:46, Tim Roberts wrote:
>>
>> I should have mentioned my test was Reportlab 3.1.44 in Python 3.4 on
>> Windows 10. Perhaps this is a Windows vs Linux thing.
> I'm running on windows 7 and this fails for me. I looked inside the ttf file and
> the unicode --> glyph mappings are strictly in a private area uF020 - uFFFF.
>
> Nothing we normally do would undo that. A special decoder encoder pair would be
> required.
>
> It's possible that the older version of reportlab was doing something integer
> bases that failed, but since you are using python 3.4 I'm not sure that can be true.
>
> Did you install the font?
OK, I can explain this now. Instead of following the link from the
original mail, I Googled code128.ttf and found this:
http://www.dafont.com/code-128.font
THAT code128.ttf file does not use the private range. It's in the
normal ASCII region.
--
Tim Roberts, [email protected]
Providenza & Boekelheide, Inc.