Re: Symbola font (was: James Kass and Code2000 font)
On 24 October 2010 14:45, Peter Constable peter...@microsoft.com wrote: And I'd advise people to upgrade from Windows XP. The snide remark seems a little uncalled for. There are many reasons why people cannot or will not upgrade from XP, and I was simply pointing out an issue that may affect some users. Anyhow, I would advise people to be cautious about upgrading from XP in case they accidentally upgrade to Windows 7, which many people on this list, especially anyone who wants to see any of the newly encoded emoji characters, might consider not fit for purpose: http://babelstone.blogspot.com/2010/05/prototyping-tangut-imes-or-why-windows.html Andrew
RE: Symbola font (was: James Kass and Code2000 font)
From: Andrew West [mailto:andrewcw...@gmail.com] And I'd advise people to upgrade from Windows XP. The snide remark seems a little uncalled for. There are many reasons why people cannot or will not upgrade from XP, and I was simply pointing out an issue that may affect some users. My comment was not intended to be snide. You were discussing crashes on XP; that represents both reliability and security concerns. Windows 7 is much more reliable and secure than XP. Anyhow, I would advise people to be cautious about upgrading from XP in case they accidentally upgrade to Windows 7, which many people on this list, especially anyone who wants to see any of the newly encoded emoji characters, might consider not fit for purpose: http://babelstone.blogspot.com/2010/05/prototyping-tangut-imes-or-why-windows.html You've commented on a known bug in the Windows 7 release affecting code points that were not encoded in Unicode 5.1. A fix for unsupported code points is hardly the type of thing you can expect to see mentioned in broadly-targeted information about SP1. Even so, the fix has already gone into the SP1 code. Peter
Re: Symbola font (was: James Kass and Code2000 font)
On 13 October 2010 21:41, Andrew West andrewcw...@gmail.com wrote: On 13 October 2010 17:48, Doug Ewell d...@ewellic.org wrote: At the risk of spreading unsubstantiated FUD, I experienced system crashes (BSOD) twice in one day while trying to configure the composite-font feature in BabelPad 6.0.0.0 (beta D) to use Symbola 6.00 on Windows XP SP3. Unfortunately this is a known issue with BabelPad and BabelMap, and not the fault of Symbola. This problem has been fixed in the new Unicode 6.0 versions of BabelMap and BabelPad that I finally released today. http://babelstone.blogspot.com/2010/10/babelpad-and-babelmap-version-6000.html However, further testing has indicated that standard Windows applications such as Notepad may blue screen crash on some systems when attempting to render U+1F5FD (Statue of Liberty, but replaced by a glyph for the Angel of Death in Symbola) with Symbola version 6.00 at high point sizes (pasting 12 x U+1F5FD into Notepad with font set to Symbola 72pts reliably crashes my Windows XP machine, but not my Vista machine). So I advise people to use the Symbola font with caution. Andrew
RE: Symbola font (was: James Kass and Code2000 font)
From: unicode-bou...@unicode.org [mailto:unicode-bou...@unicode.org] On Behalf Of Andrew West However, further testing has indicated that standard Windows applications such as Notepad may blue screen crash on some systems when attempting to render U+1F5FD (Statue of Liberty, but replaced by a glyph for the Angel of Death in Symbola) with Symbola version 6.00 at high point sizes (pasting 12 x U+1F5FD into Notepad with font set to Symbola 72pts reliably crashes my Windows XP machine, but not my Vista machine). So I advise people to use the Symbola font with caution. And I'd advise people to upgrade from Windows XP. Peter
Re: Symbola font (was: James Kass and Code2000 font)
On 24 October 2010 13:56, Andrew West andrewcw...@gmail.com wrote: However, further testing has indicated that standard Windows applications such as Notepad may blue screen crash on some systems when attempting to render U+1F5FD (Statue of Liberty, but replaced by a glyph for the Angel of Death in Symbola) with Symbola version 6.00 at high point sizes (pasting 12 x U+1F5FD into Notepad with font set to Symbola 72pts reliably crashes my Windows XP machine, but not my Vista machine). So I advise people to use the Symbola font with caution. Symbola has now been updated to version 6.01 which replaces the problematic glyphs at U+1F5FB through U+1F5FF with the correct glyphs, and now seems to be safe to use. Andrew
Symbola font (was: James Kass and Code2000 font)
Alan Wood alanmwood at yahoo dot co dot uk wrote: Incidentally, many of the new symbols in Unicode 6 are available in the Symbola font from George Douros, and they can be seen in Firefox: http://users.teilar.gr/~g1951d/ At the risk of spreading unsubstantiated FUD, I experienced system crashes (BSOD) twice in one day while trying to configure the composite-font feature in BabelPad 6.0.0.0 (beta D) to use Symbola 6.00 on Windows XP SP3. I don't know yet whether the problem was with the font or BabelPad (or something else), but I hadn't seen a BSOD on that machine for six months or more. Given the stability of BabelPad, even beta copies, I'm inclined to suspect the font. -- Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s
Re: Symbola font (was: James Kass and Code2000 font)
On 13 October 2010 17:48, Doug Ewell d...@ewellic.org wrote: Incidentally, many of the new symbols in Unicode 6 are available in the Symbola font from George Douros, and they can be seen in Firefox: http://users.teilar.gr/~g1951d/ At the risk of spreading unsubstantiated FUD, I experienced system crashes (BSOD) twice in one day while trying to configure the composite-font feature in BabelPad 6.0.0.0 (beta D) to use Symbola 6.00 on Windows XP SP3. I don't know yet whether the problem was with the font or BabelPad (or something else), but I hadn't seen a BSOD on that machine for six months or more. Given the stability of BabelPad, even beta copies, I'm inclined to suspect the font. Unfortunately this is a known issue with BabelPad and BabelMap, and not the fault of Symbola. The blue screen crash occurs somewhere within a call to ExtTextOutW() when sandwiched between BeginPath() and EndPath(), when an attempt is made to render one of the mega-complex glyphs in Symbola (e.g. the glyph for U+1F5FD STATUE OF LIBERTY ... which in fact is not the Statue of Liberty, which is actually at U+FFFED). This is the reason why the Unicode 6.0 betas of BabelMap/BabelPad have been taken off line, and their release delayed for a few days whilst I implement an alternate strategy. My apologies to any users who encounter this issue. Andrew