bugm17n - Bugs: bug #44584, Overzealous Checks Break Fonts


bug #44584: Overzealous Checks Break Fonts

Submitter:  None
Submitted:  Fri 20 Mar 2015 01:01:08 AM UTC
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  handa
Open/Closed:  Open
* Mandatory Fields

Add a New Comment (Rich Markup)

Comment Type & Canned Response:
       No canned response available


Fri 27 Mar 2015 09:01:51 AM UTC, comment #1: 

Thank you for the bug report.  I've just committed a fix for read_lookup_record_list().  Please try the code in the latest CVS repository.

Kenichi Handa <handa>
Project Administrator
Fri 20 Mar 2015 01:01:08 AM UTC, original submission:  

If read_lookup_record_list() in oftopen.c in package libotf returns zero, no further lookups will be read.  However, for a given input sequence of glyphs or classes of glyphs it is perfectly reasonable for no lookups to be invoked in response to a particular combination of backtrack and lookahead glyphs; this specifies that no action is to be taken in this case, whereas it may be taken for more general combinations of backtrack and lookahead glyphs.

Indeed, for modularity when trying out various techniques to achieve the same effect, one might create a subtable which effects no changes but merely inhibits other subtables of the same chained context table.  I did this with a font that works reasonably well both on Windows and with HarfBuzz; only when I tried using it with Emacs (and thus m17n) did I encounter problems.

It is possible to work around this with one's own font by adding nugatory lookups (e.g. to replace the first input character by itself).



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by handa (Posted a comment)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.





    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2015-03-27 handa StatusNone Fixed
        Assigned toNone handa

    Back to the top

    Powered by Savane 3.9