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


Thanks again. I am planning to check these issues in virtual machine with
Windows or Linux installed, which I think would yield some more helpful
results.

I'm afraid I did not make myself clear regarding the non-Unicode support in
Windows. I am confident that my OS is set up with Unicode support. The CP
set-up is just in parallel. In fact each running Windows system has the two
encoding systems running simultaneously, typcially using CP437 for English
environments.

I will come back with test results on these issues.



-----
"雷聲 靐䨻": if you can see four Chinese characters instead of blobs or question marks than your 
browser/OS has a good support for Unicode and CJK characters! (P.S. the four chracters put together 
means "loud thunder")
--
View this message in context: 
http://nabble.documentfoundation.org/Limited-Unicode-Support-in-LibreOffice-4-1-4-2-Character-insertion-non-zero-SMP-SIP-planes-and-multi-tp4094290p4094601.html
Sent from the Users mailing list archive at Nabble.com.

-- 
To unsubscribe e-mail to: users+unsubscribe@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.