Requesting inclusion of the proposed ebuild of new korean fonts.
Created attachment 236137 [details] Proposed ebuild
Don't you mean media-fonts/nanumfont ?
(In reply to comment #2) > Don't you mean media-fonts/nanumfont ? > Is there standard package name convention about fonts?
I heard NHN corp.(nanum font distributor) will release again soon, Because, current distribution URI has no version code, but they will contain for source based OS distribution such as Gentoo!!! :) and I have a plan that split package for font type (ttf and otf). So, I'll attach new ebuilds after release.
The media-fonts/nanumfont package already exists in portage. Does it contain the same fonts as your package or different ones?
(In reply to comment #5) > The media-fonts/nanumfont package already exists in portage. Does it contain > the same fonts as your package or different ones? > media-fonts/nanumfont package contains Nanum Gothic Coding font (monospace style) exactly. and it is one of Nanum font suite. but distributed separately for programmer. My package contains Nanum Gothic (sans style)and Nanum Myeongjo(serif style). IMHO, Nanum Gothic Coding and Nanum Gothic/Myeongjo are distributed separately. so it should not be merged in one package.
Created attachment 267951 [details] Proposed ebuild Updated ebuild attached. - fetch source from debian repository. * NHN Corp. doesn't do version control yet. so replace SRC_URI (hints from cwryu@debian.org) - update license (OFL -> OFL-1.1) - bump 3.010 (it contains Gothic, Myeongjo, Pen, Brush)
Is this in portage already? * media-fonts/nanumfont Available versions: 2.0^bs (~)2.0-r1^bs {X} Homepage: http://dev.naver.com/projects/nanumfont Description: Korean monospace font distributed by NHN
(In reply to Young-Ho Cha from comment #6) > IMHO, Nanum Gothic Coding and Nanum Gothic/Myeongjo are distributed > separately. so it should not be merged in one package. I think many other font ebuilds do something similar - merge the fonts of a family in one package. It seems to be common practice. Anyway: Maybe the proposed ebuild names should be media-fonts/nanumfont-sans and media-fonts/nanumfont-serif? And the Summary line of this bugreport adjusted accordingly?
I have recently added the proportional fonts into media-fonts/nanum ebuild. I thought I had included all fonts, but apparently missed the monospaced ones, so I put nanumfont back into the repository. I'd like to follow what our Korean users want. I think that sans/serif make little sense for asian fonts, although it's equivalent terminology. It would be better to call them gothic and mincho (myeongjo in Korean, I assume). So, I propose that we either put all nanum fonts into media-fonts/nanum (my preference, easier to install and maintain), or split them into media-fonts/nanum-gothic, media-fonts/nanum-myeongjo, and media-fonts/nanum-mono. The separate ebuilds would leave the brush script/pen script fonts a little out of place, though. What do you think?
(In reply to Guilherme Amadio from comment #10) > I have recently added the proportional fonts into media-fonts/nanum ebuild. > I thought I had included all fonts, but apparently missed the monospaced > ones, so I put nanumfont back into the repository. > Thanks for resolving that issue. :-) > I'd like to follow what our Korean users want. I think that sans/serif make > little sense for asian fonts, although it's equivalent terminology. It would > be better to call them gothic and mincho (myeongjo in Korean, I assume). > You're right. It's not suitable for classify asian fonts, even though it also can be done with sans/serif(In most cases, asian font also includes alphanumerical glyphs). > So, I propose that we either put all nanum fonts into media-fonts/nanum (my > preference, easier to install and maintain), or split them into > media-fonts/nanum-gothic, media-fonts/nanum-myeongjo, and > media-fonts/nanum-mono. > The separate ebuilds would leave the brush script/pen script fonts a little > out of place, though. > > What do you think? I prefer splitted ebuilds. Usually CJK fonts are definitely large, and someone might needs just one of nanum-font set, e.g. NanumGothicCoding. For ease install, use meta-ebuild depends on that ebuilds. And, it distributed by separate packages with classification "NanumMyeongJo", "NanumGothic", and Hand-writing style at "http://hangeul.naver.com/download.nhn".
It's mentioned on comment #6 above... ''' > media-fonts/nanumfont package contains Nanum Gothic Coding font (monospace style) exactly. and it is one of Nanum font suite. but distributed separately for programmer. (...omit...) > IMHO, Nanum Gothic Coding and Nanum Gothic/Myeongjo are distributed separately. so it should not be merged in one package. '''
> > So, I propose that we either put all nanum fonts into media-fonts/nanum (my > > preference, easier to install and maintain), or split them into > > media-fonts/nanum-gothic, media-fonts/nanum-myeongjo, and > > media-fonts/nanum-mono. > > The separate ebuilds would leave the brush script/pen script fonts a little > > out of place, though. > > > > What do you think? > > I prefer splitted ebuilds. Usually CJK fonts are definitely large, and > someone might needs just one of nanum-font set, e.g. NanumGothicCoding. For > ease install, use meta-ebuild depends on that ebuilds. And, it distributed > by separate packages with classification "NanumMyeongJo", "NanumGothic", and > Hand-writing style at "http://hangeul.naver.com/download.nhn". Alright, I will separate the ebuilds into nanum-myeongjo, nanum-gothic, nanum-coding, and nanum-brush later. For now, I am closing this bug, since all fonts are available through media-fonts/nanum (myeongjo, gothic, brush), and nanumfont (monospace). Then media-fonts/nanum can become a meta-ebuild that depends on the others.
