ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "L.S.-Soc&Gam" <axteffekt@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Graphics not being aligned correctly in natural tables
Date: Tue, 17 May 2016 21:44:36 +0200	[thread overview]
Message-ID: <573B74A4.1010200@gmail.com> (raw)
In-Reply-To: <CAG5iGsBu-fMukCkhEh5uv0SCw02WHA-aROWMo_vMX_oh+aDSdA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1622 bytes --]

Hi Luigi,

I am afraid that "mwe..." doesn't help.

Thanks tho bro,

Sebastian




Am 17.05.2016 um 18:55 schrieb luigi scarso:
>
>
> On Tue, May 17, 2016 at 6:47 PM, cryo shock <axteffekt@gmail.com 
> <mailto:axteffekt@gmail.com>> wrote:
>
>     Hello fellow ConTeXt lovers,
>
>     I am having trouble with placing graphics in between \bTD and
>     \eTD. I am using the \externalfigure to do so which works great.
>     The problem is that they aren't being aligned at all when i use
>     \setupTABLE[align={middle,lohi}] whereas text is being aligned
>     perfectly in the middle of each cell.
>     I found out that one can use \dontleavehmode\externalfigure to
>     force alignment, which als works. But when I use \dontleave... the
>     graphic isn't being placed perfectly in the middle but slightly a
>     little bit more to the top of the cell.
>     It's not a real problem for me but since everything looks great in
>     the document, the slightly to the top moved graphics bother me
>     somehow.
>     Does anybody know a workaround maybe?
>
>     Greets, Sebastian
>
> mwe...
>
>
> -- 
> luigi
>
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 3397 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2016-05-17 19:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 16:47 cryo shock
2016-05-17 16:55 ` luigi scarso
2016-05-17 19:44   ` L.S.-Soc&Gam [this message]
2016-05-17 19:50     ` luigi scarso
2016-05-17 20:22       ` L.S.-Soc&Gam
2016-05-17 21:05         ` Wolfgang Schuster
2016-05-17 22:58           ` [SOLVED] " L.S.-Soc&Gam

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=573B74A4.1010200@gmail.com \
    --to=axteffekt@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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).