mailing-list for TeXmacs Users

[Karl Hegbloom <address@hidden>]

Have a look at the attached screenshots, 3 of TeXmacs, and 1 of evince showing a PDF with outlines. The source document is also attached, so you can look at it with a text editor to see what's inside of it. There are not any with-wrapped items affecting font changes, only the global document font setting is changed between screenshots. The document itself is not changed between changing fonts.

Interestingly, the pasted unicode ¶ looks different from the one entered using the Ibus table "compose" method, where you can push P space to get the paragraph sign. When I use Ibus, I get the same resulting glyph as typing \paragraphsign Enter. But when I use Ibus to enter it into a terminal, then highlight and paste those into TeXmacs, I get a different glyph. When the global document font is one of the (correct me if I'm wrong) unicode encoded fonts, the pasted glyphs show up correctly. When that font is cork encoded, I get the wrong resulting glyph displayed.

So there's something happening differently between Ibus and TeXmacs and the pasting from the clipboard and TeXmacs; and that is not affected by which font is the document global font at the point in time when the Ibus input or pasted input occurs. The document font affects which glyph is displayed when TeXmacs has the same information in it's document tree; what is in that tree depends on which method of inputting the character was used.

On Sat, Jun 11, 2016 at 9:44 AM Karl Hegbloom <address@hidden> wrote:

PS: so unicode fonts work but cork ones don't,  I guess. I don't know for sure.  I guess.

On Sat, Jun 11, 2016, 09:43 Karl Hegbloom <address@hidden> wrote:

I also found that \paragraphmark in a paragraph heading (I redefined the paragraph macro to number them using the paragraphsign) makes a ü in the PDF outlines. I had to wrap the paragraphsign with a font change to palatino to make it look right and to get the right glyph in the pdf outlines. It used to work with cmr, but somewhere along the line I noticed it changed. It will take half a day to search revisions for the commit that broke it.

On Sat, Jun 11, 2016, 09:37 Karl Hegbloom <address@hidden> wrote:

Why will it make math look bad? And I thought that is using the system wide tex fonts installed by Ubuntu's texlive.

On Sat, Jun 11, 2016, 05:20 philippe joyez <address@hidden> wrote:

Hi Karl,

Yeah, given that other fonts correctly distinguish paragraph and section
marks, it looks like an issue with the font itself which seems to use the
same glyph for both (or the code it behaving differently -and wierdly- for
that specific font...).

If you insist on using computer modern roman here is a workaround: Install
cmr from another source on your system, update the font database and use the
that new font in place of TeXmacs'. Note however that if you do this for a
whole document math will look really bad.

Philippe

Attachment: Screenshot from 2016-06-11 10-04-17.png
Description: PNG image

Attachment: Screenshot from 2016-06-11 10-02-01.png
Description: PNG image

Attachment: Screenshot from 2016-06-11 10-02-50.png
Description: PNG image

Attachment: Screenshot from 2016-06-11 10-11-49.png
Description: PNG image

<TeXmacs|1.99.4>

<style|tmdoc>

<\body>
  <section|Ÿ<paragraphsign> \<paragraph\>Ÿ>

  <paragraphsign> Ÿ <math|\<longleftarrow\>> Document Font Stix, Ibus table
  "compose", typed <key|P space> then <key|S space>

  <paragraphsign> Ÿ <math|\<longleftarrow\>> Document Font CMR, same input;
  both look fine.

  \<paragraph\>Ÿ <math|\<longleftarrow\>> Document Font CMR, Same input into
  terminal, highlight with mouse, then paste into TeXmacs

  \<paragraph\>Ÿ <math|\<longleftarrow\>> Document Font Stix, Same input,
  pasted into TeXmacs.

  \;

  Font is Gyre Termes for this screenshot.
</body>

<\initial>
  <\collection>
    <associate|font|termes>
    <associate|font-base-size|12>
    <associate|math-font|math-termes>
    <associate|page-type|letter>
  </collection>
</initial>