Re: OPen Type Korean (Hangul) Fonts

2010-07-06 Thread Glenn Adams
On Wed, Jul 7, 2010 at 2:26 AM, Vincent Hennebert wrote:

>
> It must be seen whether advanced typography is needed to properly
> typeset Korean (for example, glyph shaping like in Arabic). Advanced
> typographic tables are not used by FOP’s layout engine at the moment.
> That may make the issue much more complicated.
>
>
Advanced typography support from fonts (e.g., GSUB/GPOS tables) is NOT
required to support common encoding of Korean, which in almost all cases
employs umgeol (syllable) instead of jamo (consonant/vowel) coding. In
Unicode, umgeol characters are encoded in the BMP range 0xAC00 to 0xD7AF,
while combining jamo are at 0x1100 to 0x11FF. Formatting the former requires
the same level of typographic support as CJK Han characters, which amounts
to little more than allowing line breaks at any character boundary (unless
one is doing Japanese with JISX4051 rules). In contrast, formatting the
combining jamo encoding of Korean requires a large ligature table or
equivalent logic (to map sequences of combining jam to corresponding
umgeol).

As a historical aside, Unicode originally supported only combining jamo,
which would indeed have forced advanced character to glyph mapping support;
however, Microsoft Korea successfully pushed through the only non-backward
compatible change to Unicode to bring in the entire block of 11,183 umgeol
syllables. In retrospect, adding he umgeol was the right move.

Regards,
Glenn


Re: OPen Type Korean (Hangul) Fonts

2010-07-06 Thread Tom Browder
On Tue, Jul 6, 2010 at 13:26, Vincent Hennebert  wrote:
...
> No, GPL is not compatible with the Apache license. We wouldn’t be able
> to ship those fonts with FOP.
> Anyway, I’m not sure that that bitmap font is what you want. I don’t
> know how FontForge does to convert a bitmap font into a vectorial font,
> but the result is likely to be unsatisfying.

I did find that the same place has a TrueType version already.

> format, like Type 1, TrueType or OpenType. Linux distribution usually
> come with loads of fonts for many languages. For example, check out this
> one for Hangul:
> http://packages.debian.org/sid/ttf-alee

Good catch--I hadn't been able to find that in my searches.

> fonts are. OpenType fonts based on CFF glyphs are not supported at all.
>
> It must be seen whether advanced typography is needed to properly
> typeset Korean (for example, glyph shaping like in Arabic). Advanced
> typographic tables are not used by FOP’s layout engine at the moment.
> That may make the issue much more complicated.

>From what I've found so far, it looks like advanced type setting will
be needed (but I think it would be fun).

Thanks, Vincent.

-Tom


Re: OPen Type Korean (Hangul) Fonts

2010-07-06 Thread Vincent Hennebert
Hi Tom,

(FWIW, I think this list is appropriate for this discussion as it has to
do with enhancing FOP.)

Tom Browder wrote:
> I would like to be able to use a Hangul (Hangeul: Korean) Open Type
> font with fop.
> 
> I have found the Unifoundry and it has Hangul fonts in bfd format.
> The licensing statement from the web site
> (http://unifoundry.com/index.html):
> 
> 
> 
> My software and is released under the terms of the GNU General Public
> License (GNU GPL) version 2.0, or (at your option) a later version.
> The precompiled fonts are released under the terms of the GNU GPL
> version 2, with the exception that embedding the font in a document
> does not in itself bind that document to the terms of the GPL.
> 
> 
> 
> It seems to me that fontforge could be used to convert the bfd fonts
> to a vector Open Type format.  If so, would their license permit them
> to be used for fop use and testing?

No, GPL is not compatible with the Apache license. We wouldn’t be able
to ship those fonts with FOP.

Anyway, I’m not sure that that bitmap font is what you want. I don’t
know how FontForge does to convert a bitmap font into a vectorial font,
but the result is likely to be unsatisfying.

I think you want to find a font directly available in a vectorial
format, like Type 1, TrueType or OpenType. Linux distribution usually
come with loads of fonts for many languages. For example, check out this
one for Hangul:
http://packages.debian.org/sid/ttf-alee
The license seems to be MIT, which would allow us to store it in our
code repository for testing purpose.

On my system, I have an “UnBatang” font that is a TrueType font and
should be supported by FOP.


> Next question, could anyone working on the Open Type area in fop use
> some help to move toward being able to use such fonts?

We certainly welcome help in improving the font system. OpenType fonts
containing TrueType glyphs are supported the same way as normal TrueType
fonts are. OpenType fonts based on CFF glyphs are not supported at all.

It must be seen whether advanced typography is needed to properly
typeset Korean (for example, glyph shaping like in Arabic). Advanced
typographic tables are not used by FOP’s layout engine at the moment.
That may make the issue much more complicated.


> Thanks.
> 
> -Tom
> 
> Thomas M. Browder, Jr.
> Niceville, Florida
> USA

Vincent


Re: OPen Type Korean (Hangul) Fonts

2010-07-06 Thread Chris Bowditch

Tom Browder wrote:

On Mon, Jul 5, 2010 at 09:48, Chris Bowditch  wrote:

Tom Browder wrote:

...

Next question, could anyone working on the Open Type area in fop use
some help to move toward being able to use such fonts?


Well, I thought that only a dev would be interested.


The devs all participate in the users list too!



I found an open bug (can't find at the moment) about not having a
suitable open type for testing.


The main barrier to using Open Type Fonts in FOP is the limitation
pertaining to CFF glyphs. FOP currently doesn't OTF with CFF glyphs. All the
eastern typefaces shipped as OTF that I have seen contain CFF glyphs.


Is anyone working on that or is that an area someone could help with?


I believe Vincent is working on that, on the TrueType In Postscript branch.

Thanks,

Chris



-Tom






Re: OPen Type Korean (Hangul) Fonts

2010-07-05 Thread Tom Browder
On Mon, Jul 5, 2010 at 09:48, Chris Bowditch  wrote:
> Tom Browder wrote:
...
>>
>> Next question, could anyone working on the Open Type area in fop use
>> some help to move toward being able to use such fonts?

Well, I thought that only a dev would be interested.

I found an open bug (can't find at the moment) about not having a
suitable open type for testing.

>
> The main barrier to using Open Type Fonts in FOP is the limitation
> pertaining to CFF glyphs. FOP currently doesn't OTF with CFF glyphs. All the
> eastern typefaces shipped as OTF that I have seen contain CFF glyphs.

Is anyone working on that or is that an area someone could help with?

-Tom


Re: OPen Type Korean (Hangul) Fonts

2010-07-05 Thread Chris Bowditch

Tom Browder wrote:

I would like to be able to use a Hangul (Hangeul: Korean) Open Type
font with fop.


Hi Tom,

Please post questions relating to the usage of FOP in the fop-users 
mailing list. fop-dev is for Java coding issues on the FOP project. Thanks!






It seems to me that fontforge could be used to convert the bfd fonts
to a vector Open Type format.  If so, would their license permit them
to be used for fop use and testing?

Next question, could anyone working on the Open Type area in fop use
some help to move toward being able to use such fonts?


The main barrier to using Open Type Fonts in FOP is the limitation 
pertaining to CFF glyphs. FOP currently doesn't OTF with CFF glyphs. All 
the eastern typefaces shipped as OTF that I have seen contain CFF glyphs.


Chris