[bug #65111] [gropdf] "warning: Using nospace mode for font 'EURO'"

[G. Branden Robinson]

Update of bug #65111 (group groff):

Category:   Font - others/general => Driver gropdf  

___

Follow-up Comment #4:

Reclassifying since it was merely an issue with a _gropdf_ diagnostic.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/


signature.asc
Description: PGP signature

[bug #65111] [gropdf] "warning: Using nospace mode for font 'EURO'"

[G. Branden Robinson]

Update of bug#65111 (group groff):

  Status: In Progress => Fixed  
 Open/Closed:Open => Closed 
 Planned Release:None => 1.24.0 

___

Follow-up Comment #3:


2024-01-03  G. Branden Robinson 

[gropdf]: Add "notice" diagnostic level for debugging.

* src/devices/gropdf/gropdf.pl (Notice): Add new subroutine.  It
emits a diagnostic message only if debugging ("gropdf -d").
(Warn): Prefix diagnostic with severity level here...
(Msg): ...instead of here.
(LoadFont): Demote diagnostic about fonts lacking space glyphs
from warning to ntoice.

Fixes .




___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[bug #65111] [gropdf] "warning: Using nospace mode for font 'EURO'"

[G. Branden Robinson]

Update of bug#65111 (group groff):

  Status:None => In Progress
 Assigned to:None => gbranden   


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[bug #65111] [gropdf] "warning: Using nospace mode for font 'EURO'"

[G. Branden Robinson]

Follow-up Comment #2, bug#65111 (group groff):

Hi Deri,

[comment #1 comment #1:]
> As I have documented elsewhere gropdf has to behave a little
> differently if a particular font does not define a space glyph. 

That statement does sound familiar.

The idea of a "space glyph" is a difficult fit for *roff-descended
typography.

> This is because it can use a slightly more compact format if the font
> defines "space" or "u0020" as a glyph. In a "Hello World" example the
> difference is "(Hello World)" (glyph defined) and "(Hello) move
> horizontal (World)" (glyph undefined).

As you know, the latter is the only way a space is represented in *roff
internally and in device-independent output ("trout", "grout").

> The distance moved is set by troff, I assume this is the purpose of
> spacewidth in the groff font.

Yes.

> Some CJK fonts also don't have a space glyph. It is just a warning,
> and was useful in debugging, to know gropdf had switched to a slightly
> less efficient output format, the message could be removed, although
> knowing which mode gropdf was operating in if I am debugging a user's
> issue could be useful.

Since there is nothing the user normally needs to do, or even _can_ do
without undertaking a mild form of digital font development, I would
prefer that we demote this from a warning to debugging output.

It strikes me as somewhat similar to the erstwhile "can't write node in
transparent throughput" and the other diagnostic like that; the user
isn't asking for nonsense, and is powerless to do anything about the
diagnostic.

What do you think?

Regards,
Branden



___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[bug #65111] [gropdf] "warning: Using nospace mode for font 'EURO'"

[Deri James]

Follow-up Comment #1, bug#65111 (group groff):

As I have documented elsewhere gropdf has to behave a little differently if a
particular font does not define a space glyph. This is because it can use a
slightly more compact format if the font defines "space" or "u0020" as a
glyph. In a "Hello World" example the difference is "(Hello World)" (glyph
defined) and "(Hello) move horizontal (World)" (glyph undefined). The distance
moved is set by troff, I assume this is the purpose of spacewidth in the groff
font. Some CJK fonts also don't have a space glyph. It is just a warning, and
was useful in debugging, to know gropdf had switched to a slightly less
efficient output format, the message could be removed, although knowing which
mode gropdf was operating in if I am debugging a user's issue could be useful.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[bug #65111] [gropdf] "warning: Using nospace mode for font 'EURO'"

[G. Branden Robinson]

URL:
  

 Summary: [gropdf] "warning: Using nospace mode for font
'EURO'"
   Group: GNU roff
   Submitter: gbranden
   Submitted: Wed 03 Jan 2024 12:40:51 PM UTC
Category: Font - others/general
Severity: 3 - Normal
  Item Group: Warning/Suspicious behaviour
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
 Planned Release: None


___

Follow-up Comments:


---
Date: Wed 03 Jan 2024 12:40:51 PM UTC By: G. Branden Robinson 
Seen during _groff_ build.  The Euro glyphs show up fine.


gropdf:man/groff_char.7: warning: Using nospace mode for font 'EURO'


Figure out what do about this.







___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/