Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi all!


There's a trouble opening simple RTF file in LO 3.4.2. It is opened, but
it's rendering is incorrect. Same file is correctly opened by MSO 2010. May
someone provide feedback on the issue? 


For reference:


Image ofLO 3.4.2 with opened file 96.rtf
http://nabble.documentfoundation.org/file/n3355881/file_96_in_libreoffice_342.jpg 


Image of MSO 2010 with opened file 96.rtf
http://nabble.documentfoundation.org/file/n3355881/file_96_in_mso_2010.jpg 


Original RTF file: 
http://nabble.documentfoundation.org/file/n3355881/96.rtf 96.rtf 


Another problematic RTF file (incorrectly rendered table in LO 3.4.2): 
http://nabble.documentfoundation.org/file/n3355881/requisites_table_in_russian.rtf
requisites_table_in_russian.rtf 


Have anybody encountered with the issue?ark@yandex.ru



--
View this message in context: 
http://nabble.documentfoundation.org/RTF-files-rendering-huge-differencies-in-LO-3-4-2-and-MSO-2010-bug-tp3355881p3355881.html
Sent from the Users mailing list archive at Nabble.com.
-- 
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


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.