Maybe not the right forum ?
but is this new encoding behaviour intentional or a issue ?
since 3.6.3 LO no longer shows correctly non-standard-ascii characters
with text imported from a database using Windows 1252 encoding(during
the import), UTF-8 encoding now works fine but gives problems when
exporting to PDF.
Older an recent files with text imported with a Windows 1252 encoding
give problems when exporting to PDF,
Some fonts like Futura Sdt (Opentype) has only the "Latin 1252" code
page and do not shows up when opening in a standard PDF viewer an do not
print when using a PDF engine.
the Adobe Viewers gives the famous error "Can not extract the embedded
fond 'FAAAAA+FuturaStdMedium' some characters........"
We found this behaviour on Windows XP machines, PDF exported on Windows
7 do not have this problem ?
The faulty PDF export is a regression starting from LO 3.6.3 and also
present in LO 3.4 beta.
ok: Window XP is a ending story, but maybe someone has the same problems
with non-Windows machines
Greetz
Fernand
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-users] LibreOffice no longer works with Windows 1252 encoding ? · Fernand Vanrie
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.