Re: symb-uni.tex (was: degree sign)
Maybe the dev list is a better place for this follow-up. I'm trying to understand (a) what exactly the task is to create the maths vectors, and (b) what is really going on with the degree sign. Taking (b) first... Looking in unic-000.tex (the degree sign is #00B0 = char 176 in vector 0) I see two vector definitions. Does the second supersede the first or are both needed? Looking at the second vector definition, it starts at char 159 and so looking down to position 176 there appears to be the correct code - namely \textdegree. This presumably explains why it appears correctly in running text in my sample posted to the ConTeXt list. But why does it not work in the XMLdata section? Is it the case that there is another unicode processing system for data being processed as XML? Is this where the fix is required? As to question (a) - for example what exactly should I put into, say unic-034.tex to denote #222A (character 42 in vector 34) as \cup? Do I need two \startunicodevector commands? Or do i just do \startunicodevector 34 \unknownchar \or ... [repeat 41 times] ... \cup \or ... \stopunicodevector ? Sorry if this betrays a lack of understanding. Look forward to clarification. Duncan Adam Lindsay (23/11/2004 13:42) said:
Duncan Hothersall wrote:
I have been searching in the base files but can't see the hook. Can anyone point me in the right direction to fix this? Thanks.
we (you -) need to define unic-*.tex vectors for the math ranges,
The attached symbol file might be a place to start. (didn't bother with list, cos file's to big)
Duncan Hothersall wrote:
Maybe the dev list is a better place for this follow-up.
I'm trying to understand (a) what exactly the task is to create the maths vectors, and (b) what is really going on with the degree sign.
Taking (b) first...
Looking in unic-000.tex (the degree sign is #00B0 = char 176 in vector 0) I see two vector definitions. Does the second supersede the first or are both needed?
the second one is the fast alternative; i always keep the previous versions of implementations for educational purposes; take whatever you like most, i can change them afterwards
Looking at the second vector definition, it starts at char 159 and so looking down to position 176 there appears to be the correct code - namely \textdegree. This presumably explains why it appears correctly in running text in my sample posted to the ConTeXt list. But why does it not work in the XMLdata section? Is it the case that there is another unicode processing system for data being processed as XML? Is this where the fix is required?
hm, aren't the math chars in another vector then?
As to question (a) - for example what exactly should I put into, say unic-034.tex to denote #222A (character 42 in vector 34) as \cup? Do I need two \startunicodevector commands? Or do i just do
\startunicodevector 34 \unknownchar \or ... [repeat 41 times] ... \cup \or ... \stopunicodevector
one option is to make a full vector (255 codes) with unknowns and to fill then stepwise the offset calculations are just optimizations Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
the second one is the fast alternative; i always keep the previous versions of implementations for educational purposes; take whatever you like most, i can change them afterwards
Right, that makes sense. I'll use the second one.
Looking at the second vector definition, it starts at char 159 and so looking down to position 176 there appears to be the correct code - namely \textdegree. This presumably explains why it appears correctly in running text in my sample posted to the ConTeXt list. But why does it not work in the XMLdata section? Is it the case that there is another unicode processing system for data being processed as XML? Is this where the fix is required?
hm, aren't the math chars in another vector then?
Most of them are, but the most commonly used (I guess?) are in 0. Any idea what might be creating the $^$ output when the textdegree character is used in XML? Looks like it maybe isn't a unicode problem?
\startunicodevector 34 \unknownchar \or ... [repeat 41 times] ... \cup \or ... \stopunicodevector
one option is to make a full vector (255 codes) with unknowns and to fill then stepwise
Great, understood. I'll get onto this then. Thanks, Duncan
Duncan Hothersall wrote:
Most of them are, but the most commonly used (I guess?) are in 0. Any idea what might be creating the $^$ output when the textdegree character is used in XML? Looks like it maybe isn't a unicode problem?
smells like a math font problem: the unicode maps on a symbol so, first we need to make a couple of examples using all kind of unicode chars in math mode Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hi, Here's a one-line change from me, it makes --version correctly identify the pdfxtex executable. Greetings, Taco [taco@boo web2c]$ diff ~/texmf/scripts/context/perl/texexec.pl /usr/TeX/texmf-dist/scripts/context/perl/texexec.pl 2789c2789 < { /^\s*This is (.*pdf(|e|x)TeX.*?)$/o and $texengine = $1 ; ---
{ /^\s*This is (.*pdf(|e)TeX.*?)$/o and $texengine = $1 ;
Hans, Would it be possible for a future version of mptopdf.pl to start using texexec.ini? I have for tetex set TeXExecutable to pdfxtex but that broke mptopdf, since the use of pdfetex is currently hardwired into the script (texexec generates mptopdf.fmt, so the fmt was created using pdfxtex). Greetings, Taco
Taco Hoekwater wrote:
Hans,
Would it be possible for a future version of mptopdf.pl to start using texexec.ini? I have for tetex set TeXExecutable to pdfxtex
but that broke mptopdf, since the use of pdfetex is currently hardwired into the script (texexec generates mptopdf.fmt, so the fmt was created using pdfxtex).
you can also use: texexec --fig=c somefile.1 Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (3)
-
Duncan Hothersall -
Hans Hagen -
Taco Hoekwater