documentation-packages team mailing list archive

[Matthew Paul Thomas <mpt@xxxxxxxxxxxxx>]

** Summary changed:

- [nc] Some characters too wide with default fixed-with font
+ Missing characters in monospace fonts fall back to proportional fonts

** Description changed:

- The character "▷" (Unicode code point U+25B7, "white right-pointing
- triangle") takes up more space than other characters.  It extends
- outside of its bounding box such that it overlaps with the character
- immediately to its right.
+ gnome-terminal 3.0.1-0ubuntu3, Ubuntu 11.10
+ gnome-terminal 3.6.2-0ubuntu1, Ubuntu 15.04
  
- Please see the attached screen shot for an example of the triangle
- overlapping with the character 'M'.
+ When a character is not present in whichever monospace font you are
+ using, Ubuntu chooses a proportional font to render it.
  
- This triangle character is not the only one that is drawn too wide.
- U+25B6 is (somewhat trivially) another example. An even better example
- is the drachma sign, U+20AF, which overlaps the character that follows
- entirely.
+ This is usually not desirable. In a terminal, for example, the
+ proportional character is often too wide and therefore overlapped by the
+ following character.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 11.10
- Package: gnome-terminal 3.0.1-0ubuntu3
- ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
- Uname: Linux 3.0.0-16-generic x86_64
- NonfreeKernelModules: nvidia
- ApportVersion: 1.23-0ubuntu4
- Architecture: amd64
- Date: Wed Feb 15 10:05:54 2012
- ExecutablePath: /usr/bin/gnome-terminal
- InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
- SourcePackage: gnome-terminal
- UpgradeStatus: No upgrade log present (probably fresh install)
+ For example:
+ - bug 819708 (heavy line-drawing characters not lined up in Ubuntu Mono)
+ - bug 1116428 ('DOTTED CIRCLE' and 'BLACK CIRCLE' substituted from a wider font)
+ - bug 1094434 ("font lacks that symbols and use the ones from the other font which have incorrect sizes")
+ - bug 736613 ("the ! is rendered on top of the C")
+ - this bug as originally reported (U+25B7 white right-pointing triangle and U+20AF drachma overlapping with following characters).
+ 
+ This happens with multiple monospace fonts -- Droid Sans Mono, Terminus,
+ TlwgMono Medium, and Ubuntu Mono -- suggesting that it is a problem with
+ fontconfig, rather than with the individual fonts.

** Project changed: ubuntu-font-family => fontconfig (Ubuntu)

** Changed in: fontconfig (Ubuntu)
       Status: Incomplete => Confirmed

** No longer affects: fonts-tlwg (Ubuntu)

** No longer affects: ttf-droid (Ubuntu)

** No longer affects: ubuntu-font-family-sources (Ubuntu)

** No longer affects: xfonts-terminus (Ubuntu)

-- 
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-font-family-
sources in Ubuntu.
https://bugs.launchpad.net/bugs/932958

Title:
  Missing characters in monospace fonts fall back to proportional fonts

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  gnome-terminal 3.0.1-0ubuntu3, Ubuntu 11.10
  gnome-terminal 3.6.2-0ubuntu1, Ubuntu 15.04

  When a character is not present in whichever monospace font you are
  using, Ubuntu chooses a proportional font to render it.

  This is usually not desirable. In a terminal, for example, the
  proportional character is often too wide and therefore overlapped by
  the following character.

  For example:
  - bug 819708 (heavy line-drawing characters not lined up in Ubuntu Mono)
  - bug 1116428 ('DOTTED CIRCLE' and 'BLACK CIRCLE' substituted from a wider font)
  - bug 1094434 ("font lacks that symbols and use the ones from the other font which have incorrect sizes")
  - bug 736613 ("the ! is rendered on top of the C")
  - this bug as originally reported (U+25B7 white right-pointing triangle and U+20AF drachma overlapping with following characters).

  This happens with multiple monospace fonts -- Droid Sans Mono,
  Terminus, TlwgMono Medium, and Ubuntu Mono -- suggesting that it is a
  problem with fontconfig, rather than with the individual fonts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/932958/+subscriptions