Re: [HarfBuzz] Don't render control characters?

Lets continue this particular discussion here: https://github.com/behdad/harfbuzz/commit/81ef4f407d9c7bd98cf62cef951dc538b13442eb#commitcomment-9469767 I want to come to a conclusion on this one as well. b On 15-03-28 10:38 AM, Konstantin Ritt wrote: > This seems to be deferred for ever :) > Wi

Re: [HarfBuzz] Don't render control characters?

This seems to be deferred for ever :) With the latest HarfBuzz, I still have to fix-up glyph/metrics for the White_Spaces of GC=Cc|Zl|Zp to avoid the "missing glyph" boxes on rendering. >From http://www.unicode.org/faq/unsup_char.html#2 : > Q: Which characters should be displayed as a visible but

Re: [HarfBuzz] Don't render control characters?

Thanks James and Jonathan for taking care of this on the CSS side. Working-group resolved to change this to display Cc characters (other than HT, LF, CR): http://log.csswg.org/irc.w3.org/css/2014-09-08/#e469835 On 14-03-20 03:19 AM, James Clark wrote: > On Thu, Mar 20, 2014 at 6:04 AM, Behdad E

Re: [HarfBuzz] Don't render control characters?

2014-03-20 3:19 GMT+02:00 James Clark : > On Thu, Mar 20, 2014 at 6:04 AM, Behdad Esfahbod wrote: > >> >> WDYT? >> > > I think the default should be to do what Unicode says. Also ask the CSS3 > text folks why they are proposing this handling of Cc. > > +1 _

Re: [HarfBuzz] Don't render control characters?

On Thu, Mar 20, 2014 at 6:04 AM, Behdad Esfahbod wrote: > > Also, Unicode says GC=Cc should just render as boxed if not supported. However, it also says that characters with the White_Space property true it should be rendered as space. In addition to 0x9, 0xA and 0xD (which both CSS and HTML

Re: [HarfBuzz] Don't render control characters?

On 14-03-06 02:20 PM, Richard Wordingham wrote: > On Thu, 6 Mar 2014 22:38:07 +0200 > Konstantin Ritt wrote: > >> Did you meet any single font with glyph for U+0008 (BS)? Honestly, I >> don't imagine what U+0008 glyph representation looks like :) > > Back one space! The underlining in Unix man

Re: [HarfBuzz] Don't render control characters?

2014-03-07 1:20 GMT+02:00 : > On Thu, 6 Mar 2014, Richard Wordingham wrote: > > On Thu, 6 Mar 2014 22:38:07 +0200 > > Konstantin Ritt wrote: > > > > > Did you meet any single font with glyph for U+0008 (BS)? Honestly, I > > > don't imagine what U+0008 glyph representation looks like :) > > > > Ba

Re: [HarfBuzz] Don't render control characters?

On Thu, 6 Mar 2014, Richard Wordingham wrote: > On Thu, 6 Mar 2014 22:38:07 +0200 > Konstantin Ritt wrote: > > > Did you meet any single font with glyph for U+0008 (BS)? Honestly, I > > don't imagine what U+0008 glyph representation looks like :) > > Back one space! The underlining in Unix man pa

Re: [HarfBuzz] Don't render control characters?

On Thu, 6 Mar 2014 22:38:07 +0200 Konstantin Ritt wrote: > Did you meet any single font with glyph for U+0008 (BS)? Honestly, I > don't imagine what U+0008 glyph representation looks like :) Back one space! The underlining in Unix man pages is usually implemented as overstrike via U+0008. Howe

Re: [HarfBuzz] Don't render control characters?

2014-03-06 21:32 GMT+02:00 Richard Wordingham < richard.wording...@ntlworld.com>: > On Wed, 05 Mar 2014 15:04:30 -0800 > Behdad Esfahbod wrote: > > > Any objection to not rendering Unicode GC=Cc, same way that we don't > > render Default_Ignorables? > > I'm not sure that BS (U+0008) and TAB (U+00

Re: [HarfBuzz] Don't render control characters?

On Wed, 05 Mar 2014 15:04:30 -0800 Behdad Esfahbod wrote: > Any objection to not rendering Unicode GC=Cc, same way that we don't > render Default_Ignorables? I'm not sure that BS (U+0008) and TAB (U+0009) don't need to be rendered. I can imagine a terminal emulator wanting BS for overstriking,

Re: [HarfBuzz] Don't render control characters?

Gregorio uses a text (and TeX) based system for notating gregorian chant. Its fonts are not related to unicode as it uses algorithms for chosing the character needed for rendering the right note shape (see < http://home.gna.org/gregorio/gregoriotex/fonts> the page is outdated as it's not using virt

Re: [HarfBuzz] Don't render control characters?

Good catch ;) I was wandering why these ones are expected to be handled by the user... +1 for having a flag for this. As for making it a separate flag, I'm not sure... When I was requesting PRESERVE_DEFAULT_IGNORABLES flag, I did care about two use-cases: 1) Symbol encoding support - thing that is

Re: [HarfBuzz] Don't render control characters?

On 14-03-05 03:23 PM, Olivier Berten wrote: > This might be problematic for the Gregorio project > which uses fonts where these ranges are valid > (and necessary). Can you elaborate? -- behdad http://behdad.org/ ___ Harf

Re: [HarfBuzz] Don't render control characters?

This might be problematic for the Gregorio project < http://home.gna.org/gregorio/> which uses fonts where these ranges are valid (and necessary). It doesn't use OpenType but if HB gets included by default in lualatex, this could lead to some troubles... (Élie, if you have some time to check...) O

[HarfBuzz] Don't render control characters?

Any objection to not rendering Unicode GC=Cc, same way that we don't render Default_Ignorables? That's the U+..001F and U+007F and U+0080..U+009F ones. In Chromium that would save us some trouble as currently we have to rewrite those to make sure we don't get any glyph for them. -- behdad h

Re: [HarfBuzz] Don't render control characters?

And we can have a separate flag for preserving them, doesn't have to be the same flag that is for Default_Ignorables. On 14-03-05 03:04 PM, Behdad Esfahbod wrote: > Any objection to not rendering Unicode GC=Cc, same way that we don't render > Default_Ignorables? That's the U+..001F and U+007F