Hacker News new | past | comments | ask | show | jobs | submit login

I assume you meant to write "XTF" (where X=T or O) not "XFT" then.

Although even then, using XTF as an abbreviation for TTF/OTF is highly nonstandard. Those four extra characters greatly increase the likelihood that you'll be understood






XFT it's the tecnology from X11 which allows antialiased fonts among FreeType. Add that support and you'll magically have proper fonts (and full Unicode ones) instead of the old, aliased, locale bound ones.

You confuse people when you write it as XFT, when the correct capitalisation is Xft: https://en.wikipedia.org/wiki/Xft

Also, you said:

> Add XFT support and this language would be cool to have a fast RAD development with easy crosscompilation.

Xft only works on X11, whereas "easy crosscompilation" suggests an interest in supporting multiple platforms, which normally includes platforms that don't use X11 (macOS, iOS, Android, Windows, even Linux with Wayland)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: