by Michael S. Kaplan, published on 2008/05/22 03:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2008/05/22/8519481.aspx
The other day, in response to my The song[ and the answer] remains the same blog where I explained once again how the Uniscribe font fallback list cannot be customized, regular reader/MVP/colleague/friend/Romanian/Adobian Mihai asked in a comment:
"You can't do it."
Ok, we got it.
But what about a feature request? :-)
Ordinarily I would say something like Good question! at this point. A colleague Softie on an interminable thread about "filler words" warned everyone against this with a story about a presentation where the questioner responded "I didn't ask you to rate the question" which gave me momentary pause.
But then I decided to say fuck it, I can be a judgmental type of person, and there are enough crap questions sent to this blog that few other than I ever see that I think I can distinguish between:
If this bothers you, then you are likely reading the wrong blog. :-)
Anyhow, back to Mihai's question.
I actually asked that very question of the PM who owns a lot of this stuff at a dinner at the Unicode Conference last year (with several other internal/external folks there) and he pointed out the fundamental problem here by starting to answer my question with another question.
(They say this is a Jewish thing but he is not Jewish so I guess it is just a thing!)
His question was simple: Where do they want to see this behavior?
It turns out that in most cases the place they want to see this is in documents, not UI -- things like Word, and in RichEdit controls when it is in applications.
Since Office applications and RichEdit both have their own (somewhat mutually exclusive, and very different) independent scheme for font fallback that largely ignores the one in Windows, a customizable font fallback scheme in Uniscribe as a feature would not really have a whole lot of impact for people outside of those building Windows UI, since
Internal Microsoft folks have probably seen this issue countless times in Product Studio, where a small bit of CJK in the middle of a bug description modifies the font of all of the text after the CJK.
Looking to the one case that could change and have some impact -- application developers who want impact in their own UI, note that only the higher level Uniscribe functions actually do font fallback anyway; the lower level ones require the developers to do it all themselves anyway. And they are the ones who have the most ability to just tell the system what to do and override the behavior any way they like.
So it would make their lives a little easier, sure. But this is hard to stack up as a crucial work item, under the circumstances.
Compelling? Sure. But blocking, when all that is really missing is better documentation/samples on how to do the overriding oneself? Not so much.
Anyway, this is the biggest reason why the feature request is unlikely to have a higher priority than it does -- because most Uniscribe usage probably wouldn't change. The majority of users who don't like font override behavior are complaining about the wrong component when they watch the automatic font choices within Word; nothing Uniscribe does would ever even be visible to them....
This blog brought to you by ご (U+3054, aka HIRAGANA LETTER GO)
Mihai on 22 May 2008 5:54 PM:
An example unrelated to RTF: enabling support for some scripts that are now "almost supported"
- stuff like Ethiopic, or Cherokee or Unified Canadian Aborigenal. These are not complex scripts, and having the right font is all that's needed. And even for "slightly complex scripts" (whatever that is :-) badly shaped glyphs are better than noglyph.
- stuff like SimSun-GB18030 on XP. There is no decent way that I know of to have an application show CJK Supplement A both on Vista and XP. (except for changing the dialog font at runtime/design time, each with it's own set of problems).
And in general setting the dialog font is not good for non-localized applications. I don't need an application localized into Cherokee in order to use Cherokee in a search dialog.
Michael S. Kaplan on 23 May 2008 7:11 AM:
Okay, not sure where one needs Ethiopic or Cherokee or whatever working -- where are we talking? I don't think the Ethiopic Notepad scenario that doesn't like Nyala is all *that* compelling. :-)
and if we are talking Word then we're back in that "someone else's world" issue since even if you could override, they would override your override....
Mihai on 23 May 2008 2:53 PM:
We are talking standard edit controls.
Even when using MS Word, or a proprietary RTF based solution, or even a proprietary Uniscribe-based solution, one still needs support for that script in the Find/Replace box, author name, document summary, all kind of other places.
And it is not only about Ethiopic. It is about any script that is in Unicode, needs no complex shaping, has a decent 3rd party font, but is not in Windows.
Michael S. Kaplan on 23 May 2008 5:12 PM:
Many of the ones you named (including Ethiopic) *are* supported by the platform now, which might be why I was confused here. I sincerely doubt you will ever see significant backports of these to XP, so keeping the "major improvements" conversation rooted in the next version to come. :-)
I don't disagree that everything you mention would be NICE -- but document fidelity is hardly at stake when it comes to text in a Find/Replace dialog. It is pretty easy to see why this is considered less important from a triage standpoint (and please note that any application CAN override such font settings if they decide it would be a good idea. The fact that they are not in a hurry to, that they also triage these to be less important, has some significance....
Mihai on 27 May 2008 12:44 PM:
I was looking at XP, so these are not supported.
But it is the general principle: the ability to set a font for script X before it is officially supported by the OS version Y.
There are non-complex scripts not supported in Vista.
The idea that any application can override the font fall-back of it's dialogs is far fetch though. This a complete set of custom controls (labels, edit controls, combo-boxes, buttons etc.). With all the rtl/accessibility/theme support. And that fixes one application only (and stuff will still not work in standard dialogs, or Explorer).
Now, that's a high bar (way higher than adding it to Uniscribe).
Well, it would be indeed nice.
One can dream :-)
Michael S. Kaplan on 27 May 2008 1:46 PM:
Of course, as I described in other posts, there is an undocumented sixth category for CS -- scripts that Uniscribe enables font fallback for. And those must be on Uniscribe's lists! :-)
In XP, if you know the font you can choose it, and use it. This is likely as good as downlevel support will be....
2011/06/30 Falling back can sometimes be falling over
go to newer or older post, or back to index or month or day