On 26/01/2013 12:41, Bram Moolenaar wrote:
Taro Muraoka wrote:
How about recycle an existing 'antialias' option for this purpose.
It is an option for MacOSX to control font rendering.
I know this is not good idea, but there is a platform depended option already.
Why can't we recycle it?
# 'antialias' maybe added by me so long ago, and I forgot it entirely ;)
If the effect of using DirectX is very similar to enabling antialias
then we could use that option. If it actually does something else then
it's better to use a different option.
The DirectX DirectWrite text renderer is the new font renderer on
Windows. DirectWrite text rendering particularly improves OpenType
fonts which is why fonts such as Source Code Pro and Inconsolata with
western text also improve with this patch.
DirectWrite font rendering supports additional rendering options
analogous to those supported by freetype in X(*) - LED RGB order,
sub-pixel rendering, and anti-aliasing. These are set when configuring
ClearType from the font control panel applet, but they can also be set
for individual programs as well (it may be worth adding to any doc for
this patch that best results will be obtained with ClearType enabled and
configured). It is possible that DWriteContext_SetRenderingParams() in
the patch is meant to allow setting specific rendering options from a
multi-valued option or a collection of boolean ones.
(*) gdipp (http://code.google.com/p/gdipp/) is a project using freetype
to improve general Windows text rendering. This is an alternate to the
GDI renderer, not DirectX, so may still suffer from the GDI text API
limitations, I haven't tried it.
Mike
--
Just when they think they know the answers, I change the questions.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
