ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Igor Vlasenko <vlasenko@imath.kiev.ua>
To: devel@lists.altlinux.org
Subject: Re: [devel] I: Font policy 2.0 discussion
Date: Sun, 7 Aug 2011 22:37:00 +0300
Message-ID: <20110807193700.GA9421@dad.imath.kiev.ua> (raw)
In-Reply-To: <20110802154415.GA1358@dad.imath.kiev.ua>

On Tue, Aug 02, 2011 at 06:44:15PM +0300, Igor Vlasenko wrote:

Внес упомянутые поправки в текст
http://www.altlinux.org/Fonts_Policy
прошу обсуждать на предмет принятия как действующее полиси.

> Уважаемые коллеги,
> хочу начать обсуждение поправок к font policy.
> 
> 1) с недавним появлением в fontconfig filetrigger'а 
> наконец устарели %post/un скрипты с вызовом fc-cache, 
> а также макросы %post_fonts/%postun_fonts 
> 
> соответственно, по факту надо поправить rpm-build-fonts
> и текст полиси.
> 
> 2) Установка шрифтов под core X font subsystem.
> 
> У нас, как и в большинстве других дистрибутивов,
> есть 2 подсистемы шрифтов: новая, Fontconfig, 
> и старая, core X font subsystem, которая объявлена
> legacy and broken by design.
> 
> для установки шрифта в core X font subsystem нужен fonts.dir
> и симлинк в /etc/X11/fontpath.d.
> Большинство приложений сейчас использует Fontconfig,
> включая новый emacs. core X font subsystem нужна для совместимости
> со старыми приложениями, в т. ч. Qt1/Qt2 и gtk1.
> 
> Сейчас в Сизифе все наши шрифты недискриминантно устанавливаются сразу
> под обе подсистемы, в отличие от, например, SuSE и Fedora.
> 
> Там принято устанавливать под core X font subsystem только
> растровые и избранное множество проверенных векторных шрифтов, 
> так называемые Core Fonts, мотивируя это тем, что 
> 
> а) немногим старым приложениям нужны только экранные шрифты. 
> Все, кому нужно что-то большее, уже переехали на Fontconfig.
> 
> б) установка в core X font subsystem большого числа ненужных
> художественных otf/ttf шрифтов эквивалентна DoS атаке на X сервер
> через его протухший устаревший плохо поддерживаемый модуль.
> 
> Предлагаю и нам принять такое полиси и перестать устанавливать
> новые otf/ttf шрифты в core X font subsystem по умолчанию,
> оставив там только имеющиеся шрифты. 
> 
> Если пойти дальше, может быть, и часть имеющихся тоже перевести 
> в Fontconfig-only шрифты (выбросив fonts.dir и симлинк 
> в /etc/X11/fontpath.d).
> 
> 
> Ресурсы:
> 
> http://old-en.opensuse.org/Packaging/Fonts_Policy#Core_fonts
> http://fedoraproject.org/wiki/Packaging:FontsPolicy#Core_fonts
> Core fonts
> 
> Once upon a time every Linux GUI application used the so-called Core fonts server-side X11 backend[7]. It was riddled with problems. The FLOSS developers finally gave up on it, declared it legacy and broken by design, and moved to client-side font handling (fontconfig). Nowadays almost no modern Linux GUI application uses the Core fonts backend. Few (if any) people are willing to fix its remaining bugs.
> 
> Therefore, unless your font has previously been registered in Core fonts, and the problems triggered by this font hopefully fixed, you SHOULD NOT declare it there. This is especially true of fonts in modern (TTF or OTF) formats.
> 
> The users of this legacy backend won't thank you for destabilizing it with new fonts. They value stability. Otherwise they'd have moved to fontconfig like everyone else a long time ago.
> 
> 
> 
> http://markmail.org/message/4nwmisamzgkoklnp
> 
> fonts.dir and fonts.scale are used by the old X11 "core" font backend.
> 
> http://fedoraproject.org/wiki/Packaging:FontsPolicy#Core_fonts
> 
> It's been deprecated in favour of client-side font management (fontconfig) for about 7 years (replacing the X11 core font backend with fontconfig could probably be considered the first step that lead to modern modularized xorg). Nowadays almost nothing important uses the X11 core font backend in Fedora (even emacs finally switched and emacs is not exactly an agile project)
> 
> That being said many proprietary or niche software packages still use the old system because they either do not care a lot about i18n, or about Linux, or want code that works the same way on antique 'classic' Unix systems (less-antique Unix systems use fontconfig just as Linux as every single major GUI package requires it nowadays).
> 
> If you want to expose your fonts in the core font system you'll need to include fonts.* and symlink the directory you deploy your fonts in to /etc/X11/fontpath.d/ (note that software that still uses the old font system is likely to go bang if you feed it a modern font).
> 
> Fedora-side, we're not encouraging people to register new fonts in the core font system. We're keeping just enough old core fonts to make old apps happy (and don't install them by default anymore, so people who depend on them have to request them explicitely, and not continue to ignore the software landscape has changed) 

-- 

Dr. Igor Vlasenko
--------------------
Topology Department
Institute of Math
Kiev, Ukraine


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



  parent reply	other threads:[~2011-08-07 19:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02 15:44 Igor Vlasenko
2011-08-06  9:20 ` Michael Shigorin
2011-08-07 19:37 ` Igor Vlasenko [this message]
2011-08-09 20:33   ` Aleksey Avdeev
2011-08-09 20:39     ` Igor Vlasenko
2011-08-09 20:53       ` Aleksey Avdeev
2011-08-09 21:01         ` Igor Vlasenko
2011-08-09 21:07           ` Aleksey Avdeev
2011-08-10  7:38             ` Aleksey Avdeev
2011-08-10  8:18               ` Igor Vlasenko
2011-08-10  9:02                 ` Aleksey Avdeev
2011-08-09 21:17       ` Aleksey Avdeev
2011-08-10  7:28         ` Igor Vlasenko
2011-08-13  8:12           ` Aleksey Avdeev
2011-08-13  9:18             ` Igor Vlasenko
2011-08-13  9:37               ` Aleksey Avdeev
2011-08-14 20:22   ` Igor Vlasenko
2011-08-18 13:09 ` Igor Vlasenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110807193700.GA9421@dad.imath.kiev.ua \
    --to=vlasenko@imath.kiev.ua \
    --cc=devel@lists.altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git