Comment 10 for bug 677134

Denis: at the moment I'm trying to get confirmation from Mark (without using the current semi-ambiguous textual descriptions) which we one(s) we want to prepare for wider feedback testing.

At the moment I have two early fonts in-hand since a couple of days ago which I'm trying to dogfood in my daily working. For this I have created two new profiles in Gnome-Terminal which select those two fonts, then by using screen -x (connect to an existing screen session without disconnecting the other viewer) I can have the same window/IRC/emacs visible to two terminals.

Mark also has a couple of fonts to test in-hand, but they could well be different iterations, once we have confirmation on the particular two/three directions to test, DaltonMaag can prepare the .ttfs and we can do some wider testing. At the moment neither of the iacute or iota-combining-acute _exist_ in the Ubuntu Monospace workings, so it's not possible tell if they are ambiguous or not! If you encounter these two in your daily working and find that other monospace fonts do not differentiate sufficiently, please could you file a bug against the 'mono' milestone so that special attention can be paid to that use-case (it would be useful if you could provide a sample text which uses those two codepoints in close proximity in the real world).

  https://bugs.launchpad.net/ubuntu-font-family/+filebug