There is a new (texlive-2009) release in gentoo. It however contains old and bugyy context version. Reproducible: Always Steps to Reproduce: 1.Create following file (minimal.tex) \setupoutput [pdftex] \enableregime [utf] \usetypescript [modern][ec] \setupbodyfont [ss,10pt] \mainlanguage [en] \setuppapersize [A4][A4] \setupcolors [state=start] \setuppagenumber [state=stop] \starttext \setupTABLE[background=color,backgroundcolor=white] \bTABLE \bTABLEbody \bTR[topframe=off] \bTD[nr=4,width=100pt,frame=off] Test1 \eTD \bTD[width=120pt,frame=off,rightfheight=32pt,align={right,low}] \ {\externalfigure[flcz.png] [width=20pt]} Lang1,Lang2 \eTD \bTD[width=240pt,frame=off,height=20pt,align={right,low}] result \eTD \eTR \bTR \bTD[align={right,low},height=20pt,frame=off] \ {\externalfigure[fluk.png] [width=20pt,align={right,low}]}\ Test2\eTD \bTD[align={right,low},height=20pt,frame=off] test text number 3\eTD \eTR \eTABLEbody \eTABLE \stoptext 2. run texexec minimal.tex 3. view resulting minimal.pdf Actual Results: The text is rendered below the pictures Expected Results: The text is rendered right of the pictures According to http://bugs.archlinux.org/task/17778?string=texlive&project=1&search_name=&type[0]=&sev[0]=&pri[0]=&due[0]=&reported[0]=&cat[0]=&status[0]=open&percent[0]=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= the problem is in buggy texlive version. However with the current git/svn version it works OK. texlive-2009 in gentoo needs to be updated therefore
Correct the summary with the package name that owns context subpackage.
ping?
Question- is this a regression compared to texlive 2008?
Yes, with 2008 it worked OK. It is a known bug of 2009, for example with user-installed latest context-minimals it is OK
So the solution for this bug would be installing a newer version of texlive.
Exactly, however there is no ebuild for it available in the portage.
There is bug #339098. If this is not fixed upstream, I think that we should ignore this when texlive 2010 hits portage (not before, obviously)
I think this bug will be fixed when 2010 hits portage if that's what you mean
should be fixed with texlive 2010 which will be unmasked soon