GNU TeXmacs - Bugs: bug #36086, nocomma, nospace, etc. not...
You are not allowed to post comments on this tracker with your current authentication level.
bug #36086: nocomma, nospace, etc. not recognized when not using truetype fonts
Submitter: | Miguel de Benito <mdbenito> | ||
Submitted: | Wed 04 Apr 2012 03:01:54 PM UTC | ||
Category: | Editor | Priority: | 5 - Normal |
Item Group: | Error | Status: | Works For Me |
Privacy: | Public | Assigned to: | vdhoeven |
Originator Name: | Open/Closed: | Closed | |
Release: | None | Release: | 1.0.7.15 |
Fixed Release: | None | Fixed Release: | |
Keywords: |
Fri 29 Nov 2013 05:42:37 PM UTC, comment #5: |
Joris van der Hoeven <vdhoeven> |
Wed 01 Aug 2012 01:56:36 PM UTC, comment #4: The patch was reverted because was the code was apparently too slow, so we still need some solution... |
Miguel de Benito <mdbenito> |
Mon 28 May 2012 10:07:00 PM UTC, comment #3: No comments but a problem still present lead me to apply the patch. There is still the issue of the big-, b- and c- entities. |
Miguel de Benito <mdbenito> |
Thu 05 Apr 2012 03:51:11 PM UTC, comment #2: Very nice test! I think most of the non-rendered entities in the first lines are rendered if the font provides them. Just try selecting a truetype math font.
|
Miguel de Benito <mdbenito> |
Thu 05 Apr 2012 11:59:23 AM UTC, comment #1: This also appears in X11 version, and affect many other chars. Many entities defined in TeXmacs/langs/encoding/tmuniversaltounicode.scm are not well rendered. See joint file. |
Francois Poulain <fpoulain> |
Wed 04 Apr 2012 03:01:54 PM UTC, original submission:
The check for these texmacs symbols (<nocomma>, <nospace>, etc.) is done inside unicode_math_font_rep::search_font_sub(), which is never called for non unicode fonts, like the default Roman. This results in ugly "<nocomma>"'s all over the document.
|
Miguel de Benito <mdbenito> |
Depends on the following items: None found
Items that depend on this one: None found
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.
Follow 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2013-11-29 | vdhoeven | Status | Need Info | Works For Me | |
Assigned to | mdbenito | vdhoeven | |||
Open/Closed | Open | Closed | |||
2012-08-01 | mdbenito | Status | Confirmed | Need Info | |
2012-04-05 | fpoulain | Attached File | - | Added test_tmuniversal.tm, #25586 | |
2012-04-04 | mdbenito | Attached File | - | Added patch.diff, #25570 |
Powered by Savane 3.13-cf05.
Corresponding source code
I cannot reproduce the bug concerning invisible homoglyphs on my system (that is, , <nocomma>, <nospace>, etc.; notice that <notimes> does not exist, since we use instead). I both tried using the new style fonts and the usual fonts, and both for the default font and Stix. Of course, the small calligraphic symbols and many other symbols are not systematically treated yet, so improvements on this issue can be expected when we switch to the new font system. However, I do not consider this to be a bug, but rather a missing feature, which is in progress.