ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: <mari.voipio@iki.fi>
Subject: Encoding problems and degree sign
Date: Fri, 27 Sep 2002 10:32:18 +0300 (EET DST)	[thread overview]
Message-ID: <Pine.OSF.4.30.0209271005550.10468-100000@sirppi.helsinki.fi> (raw)

This is probably almost FAQ stuff, but my skills aren't enough to solve
the problem.

My system is WindowsNT+TeXLive [May/June version] (+WinEdt/NTEmacs), the
type-enc file I stole from a newer ConTeXt as the TeXLive version had
typos and other problems.

My document uses the standard postscript fonts and this far I've been
happy with them, but yesterday I found out that the degree sign doesn't
work. From the pictures in "TeXfont Explained" I derived that the "degree
slot" (176) is occupied by something else in ec. The original text is
Windows cut-n-paste stuff (from a Word document), if that makes any
difference. Both editors show the degree sign as a degree sign.

So I tried to use texnansi encoding instead. I installed the fonts with
type-tmf.bat and my original test document came out fine with all the
diacritics and everything. I did everything the same way than with the ec
encoded fonts that work. But when I switched my big document into
texnansi, it gets so bad problems with some font sizes/types/weights that
the resulting pdf document cannot be opened at all (error messages pasted
in the end of this document).

I can think of three ways to get out of this, but I cannot figure out how
to realize any of them:

1) Instead of writing the small ring in the text, use a code for it, like
in html I would use &#176; or &#deg; - I tried with \Degree and \degree,
but either that's not the right code or I just can't use it right.

2) I'm not using the whatever occupies the slot 176 in the standard ec, so
I could just replace that with the degree sign. But from the explanations
in the various manuals and in the mailing list archives I understand that
this might not a) be a good idea and b) be possible.

3) Find out where the font problem is and fix it. I'd understand it if the
ec encoding didn't work either, but why does the ec installation work
while similar texnansi installation is somewhat dysfunctional? All the
necessary files are available and the *-raw-* files seem to be the same,
but what's wrong? Something is probably missing somewhere (type-tmf.bat?),
but what and where?

The document I'm working on needs to be finished in not-so-distant future
so I do not have much time for fighting with the fonts any more. Thus I
could do with a quick-but-not-so-elegant fix ASAP and then fix the
texnansi problems fully later, if you have any ideas of where to look.

Thank you for your help,
		Mari Voipio

All warnings I get when I try to compile my file (headings sans-serif,
various sizes and weights, text serif, at least two non-default sizes and
two font weights) with texnansi encoding:
--
Warning: pdfetex.exe (file texnansi-raw-utmri8a): Font texnansi-raw-utmri8a
at 600 not found
Warning: pdfetex.exe (file texnansi-raw-utmb8a): Font texnansi-raw-utmb8a
at 600 not found
Warning: pdfetex.exe (file texnansi-raw-utmr8a): Font texnansi-raw-utmr8a
at 600 not found
Warning: pdfetex.exe (file texnansi-raw-uhvr8a): Font texnansi-raw-uhvr8a
at 864 not found
Warning: pdfetex.exe (file texnansi-raw-utmr8a): Font texnansi-raw-utmr8a
at 360 not found
Warning: pdfetex.exe (file texnansi-raw-uhvr8a): Font texnansi-raw-uhvr8a
at 360 not found


             reply	other threads:[~2002-09-27  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27  7:32 mari.voipio [this message]
2002-09-27  9:54 ` Jens-Uwe Morawski
2002-09-27 11:48   ` mari.voipio
2002-09-27 15:12     ` Jens-Uwe Morawski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.OSF.4.30.0209271005550.10468-100000@sirppi.helsinki.fi \
    --to=mari.voipio@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).