Statistics:Posted by FWJ — Tue Feb 06, 2018 6:25 pm
Statistics:Posted by FWJ — Wed Jul 02, 2014 7:40 pm
Statistics:Posted by fHeZC5 — Tue Apr 29, 2014 6:02 am
Statistics:Posted by FWJ — Wed Mar 26, 2014 9:04 pm
Statistics:Posted by fHeZC5 — Wed Mar 26, 2014 1:45 pm
Statistics:Posted by FWJ — Wed Dec 11, 2013 3:48 am
Statistics:Posted by Sina — Tue Sep 20, 2011 3:33 pm
Statistics:Posted by Sina — Mon Jun 06, 2011 11:20 am
Statistics:Posted by FWJ — Sun Jun 05, 2011 6:23 pm
Statistics:Posted by Sina — Thu May 19, 2011 9:17 am
Statistics:Posted by FWJ — Sun May 01, 2011 11:26 pm
Windows XP has been discontinued for a while now, so why not leave the current version as it is for Windows XP - and those who wish to continue to use legacy 8-bit fonts - and make a seperate version for Unicode and Windows Vista / 7? This would avoid any problems associated with having to support Unicode and ANSI fonts in one version.FWJ wrote:I realize you only asked a simple question (a good one) but perhaps it will be useful if I explain further.
I am working on the conversion every day and have been for several months.
I have all the basics working including Unicode Copy/Paste and RTF Import.
I works pretty well on Win2K/XP/Vista, and the BO Tibetan (PRC) keyboard works on Vista.
However, there are several difficult issues to solve.
The problem is that I am trying to create a version that supports Unicode and also continues to provide support for ANSI fonts *exactly* like the current version. This is proving VERY difficult. Mostly because I want it to work correctly for any user without requiring some special system configuration.
On Windows Vista and Windows 7 there is of course no need to update or distribute the Uniscribe DLL.FWJ wrote:The standard way to display Unicode on a Windows system is with Microsoft's Uniscribe DLL (usp10.dll). Uniscribe helps a program display Unicode fonts and is very important for fonts that are considered "complex script". Unicode Tibetan is considered "complex script" and Uniscribe is able to do a good job of displaying it.
The problem is that once Uniscribe is enabled, the system code that displays older ANSI fonts starts to fail in strange ways. Even worse, the failures are dependent on what has been installed on the system. It depends on which version of the Uniscribe DLL is available on the system. As an example, about 20 characters in the TibetanMachine typeface are no longer displayed if you use certain Uniscribe versions; but do appear with other versions. Even if I find a Uniscribe version that mostly works I can't distribute it because Microsoft does not allow that.
It sure would be nice to see a version of PechaMaker that works with Unicode fonts.FWJ wrote:The task for now is to try many ways to work around these issues.
Statistics:Posted by cfynn — Thu Oct 14, 2010 5:00 am
Statistics:Posted by FWJ — Wed Sep 29, 2010 7:17 am
Statistics:Posted by cfynn — Thu Sep 03, 2009 5:55 am
Statistics:Posted by cfynn — Thu Sep 03, 2009 5:29 am