Hi Takashi,
On Wed, 30 Nov 2011 15:29:31 +0100
Takashi Iwai
[...]
Yes, that would be another possibility. However, I doubt this option would be taken into account very often. ;)
Heh. The RPM group has nowadays less meaning, but it could be improved a bit more, in general.
Yes, you're probably right, but I hardly use it.
[...]
I would appreciate it if we could make it more consistent, but I know there might be some technical issues (dependency problems, ...) that prevents from doing so.
I guess the dependency shouldn't be a big issue when we do renaming correctly.
Ok, that's good news!
[...]
Neither of the previous is a bitmap font, I guess.
Yes. In general, SUSE packages are mostly named as is of the original package name. These ttf-* are built from ttf-*.tar file. Same for gnu-unifont. It's built from gnu-unifont.tar.
Ok.
[...] But the current situation looks messy, indeed, so I'm for some consistent naming rule.
That would be helpful
And, adding -fonts to a package like gun-unifont would be strange. gnu-unifont-fonts? In most cases, prefixing would be better IMO.
Fedora uses this name: gnu-free-fonts (if this package contains the same fonts).
No, it's a different one. I guess it's "freefont" package.
Ok, thanks for the hint.
[...]
4. Probably it is useful to open a FATE request?
Sounds like a good idea.
Ok, here is the first draft: [313035] Invent Consistent Font Naming Schema https://features.opensuse.org/313035 I took the liberty to add you as interested. Feel free to change it.
So, we need to make clear: - whether we group all fonts or only specific types (ttf, bitmap, etc); if we name for ttf, what we should do for otf?
It seems neither Fedora nor Ubuntu distinguish OTF and TTF, so why should we? It make sense for bitmap vs. vector.
It's my guess, too. But a picky person would complain ;)
Maybe. :)
Another issue: Do we have a special repository dedicated only to fonts? I couldn't find any... Do you think this is useful?
Until now, fonts packages are put in M17N project in general. Moving around would be OK, but we need the proper notification.
Ok. I just looked from the usability perspective when someone wants to incorporate a repository with fonts. Where should he get it from? What's the URL? etc.
OBS M17N repo :)
Well, *I* would first look for something like "fonts". M17N doesn't have "fonts" in its name. ;-)
It was just an idea, if there technical issues than I'm totally fine with the M17N repo. :)
I find it's OK to move fonts out of M17N into an individual project. Fonts are rarely rebuilt and all noarch, thus they don't need to keep up each openSUSE release.
Right. If you don't mind, I would request such a font repository.
But, as mentioned, they are already found in M17N. So, when we move them, we need to notify users to add the new project (or make links to M17N back), otherwise they'll loose the packages.
Ok, good point. -- Gruß/Regards, Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH (o< Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://www.suse.com | HRB 21284 SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org