Oliver Buerschaper wrote:
>>> Clearly, this gives me each glyph individually but stacked on top of
>>> each other. What I need though is that the second figure looks
>>> exactly like the first one (with all glyphs in the right location)
>>> except that the grey bounding boxes appear per glyph.
>>
>> Clearly, this gives me each glyph individually but stacked on top of
>> each other. What I need though is that the second figure looks
>> exactly like the first one (with all glyphs in the right location)
>> except that the grey bounding boxes appear per glyph.
>
> I know what you want now, but
On 08/22/2010 09:53 AM, Oliver Buerschaper wrote:
Clearly, this gives me each glyph individually but stacked on top of
each other. What I need though is that the second figure looks
exactly like the first one (with all glyphs in the right location)
except that the grey bounding boxes appear per
>> Now onto step two: how can I typeset each glyph in the formula individually
>> such that it appears precisely in the right location?
>
> I must be misreading something here, but I cannot figure out what
> 'the right location' means.
Since textext() always returns a single picture that can't b
On 08/21/2010 04:24 PM, Oliver Buerschaper wrote:
Now onto step two: how can I typeset each glyph in the formula individually
such that it appears precisely in the right location?
I must be misreading something here, but I cannot figure out what
'the right location' means.
Best wishes,
Taco
>>> so, if in mkiv you want pieces, you need to textext each snippet that you
>>> want as such
>>
>> Alright... in that case how would I make sure that all glyph positions are
>> kept if my TeX material is, say, some complex formula? How could I find the
>> baseline with textext?
>
> see mp.mp
On 18-8-2010 2:20, Oliver Buerschaper wrote:
the fact that you have pieces in mkii is a side effect of dvitomp turning dvi
output in mp pictures; in the process it combines glyphs that have no kerning
and whatever spacing becomes shifts
Oh, I didn't know the pieces used to come about by accid
> I always develop a kind of romantic relationship with the tools I use, I
> either hate it and stop using it no matter what it can or can not do; I
> hate OpenOffice and Qt, for example, and I would never, willingly use
> either. On the other hand, when I love some tool I never turn my back to
> i
On Wed, Aug 18, 2010 at 02:20:51PM +0200, Oliver Buerschaper wrote:
> > the fact that you have pieces in mkii is a side effect of dvitomp turning
> > dvi output in mp pictures; in the process it combines glyphs that have no
> > kerning and whatever spacing becomes shifts
>
> Oh, I didn't know th
> the fact that you have pieces in mkii is a side effect of dvitomp turning dvi
> output in mp pictures; in the process it combines glyphs that have no kerning
> and whatever spacing becomes shifts
Oh, I didn't know the pieces used to come about by accident... actually, by a
rather favourable a
On 17-8-2010 4:32, Oliver Buerschaper wrote:
Hi,
I've been trying to troubleshoot a problem with TeX labels I ran into the other
day... finally I discovered that
1. MkIV (textext) includes TeX material as one single chunk apparently while
MkII (btex ... etex) used to include a decomposable pi
Hi,
I've been trying to troubleshoot a problem with TeX labels I ran into the other
day... finally I discovered that
1. MkIV (textext) includes TeX material as one single chunk apparently while
MkII (btex ... etex) used to include a decomposable picture and that
2. the anchor point is completel
12 matches
Mail list logo
