On 02 Aug 2014, at 18:58, Otared Kavian wrote:
> Regarding the text encodings understood by mkii and mkiv, one can always use
> UTF-8 in both.
> Unless you have some very uncommon characters in your ascii file, the
> migration from ascii to utf-8 is quite easy, at least on a Mac (I don’t know
Hi Gerben,
Regarding the text encodings understood by mkii and mkiv, one can always use
UTF-8 in both.
Unless you have some very uncommon characters in your ascii file, the migration
from ascii to utf-8 is quite easy, at least on a Mac (I don’t know what OS you
are using): for instance you can
On 02 Aug 2014, at 15:12, Gerben Wierda wrote:
> I suspected as such. I’m afraid to move to mkiv at this stage of my project.
> Is mkiv downwards compatible with mkii? What must I do to see if my project
> compiles with mkiv? I’m running currently commands like
Later for me. I read:
Mark IV n
On 01 Aug 2014, at 16:13, Otared Kavian wrote:
>> […]
>> I’ve tried to add this to my environment and product file, but even without
>> using it, it ends in an error:
>>
>> (/usr/local/texlive/2014/texmf-dist/tex/context/base/spec-tpd.mkii
>> specials: loading definition file fdf
>> (/u
On 01 Aug 2014, at 13:30, Gerben Wierda wrote:
> […]
> I’ve tried to add this to my environment and product file, but even without
> using it, it ends in an error:
>
> (/usr/local/texlive/2014/texmf-dist/tex/context/base/spec-tpd.mkii
> specials: loading definition file fdf
> (/usr/loca
On 26 Jul 2014, at 10:43, Hans Hagen wrote:
> On 7/25/2014 4:31 PM, Gerben Wierda wrote:
>> Thanks all for the discussion. As a simple user, I think I must pass. All
>> this complexity in my document text and setup is too much trouble and it
>> seems risky (wjhat am I going to break?). Far less
On 7/25/2014 4:31 PM, Gerben Wierda wrote:
Thanks all for the discussion. As a simple user, I think I must pass. All this
complexity in my document text and setup is too much trouble and it seems risky
(wjhat am I going to break?). Far less work to do a small check at the end.
Well, that kind
On 7/25/2014 4:34 PM, Rik Kabel wrote:
On 2014-07-25 07:06, Hans Hagen wrote:
On 7/24/2014 2:03 PM, Otared Kavian wrote:
Hi,
Thanks for your attention, Wolfgang: indeed removing
\analyzecurrentreference
from your example allows mkiv to typeset correctly and obtain the
expected result.
>
On 2014-07-25 07:06, Hans Hagen wrote:
On 7/24/2014 2:03 PM, Otared Kavian wrote:
Hi,
Thanks for your attention, Wolfgang: indeed removing
\analyzecurrentreference
from your example allows mkiv to typeset correctly and obtain the
expected result.
>
yet another sparsely documented f
Thanks all for the discussion. As a simple user, I think I must pass. All this
complexity in my document text and setup is too much trouble and it seems risky
(wjhat am I going to break?). Far less work to do a small check at the end.
What I was looking for was something simple that made for ins
On 7/24/2014 2:03 PM, Otared Kavian wrote:
Hi,
Thanks for your attention, Wolfgang: indeed removing
\analyzecurrentreference
from your example allows mkiv to typeset correctly and obtain the expected
result.
>
yet another sparsely documented feature ... in beta:
% tests/mkiv/pa
On Thu, Jul 24, 2014 at 1:38 PM, Wolfgang Schuster <
schuster.wolfg...@gmail.com> wrote:
>
>
> I won’t trust this pagenumber check because when a reference appears at
> the begin of a page
> it can sometimes use the pagenumber of the previous page (hard to notice
> when you use \page
> in your exa
On 2014-07-24 07:20, Otared Kavian wrote:
Hi Rik,
As a matter of fact the example given by Wolfgang works despite mkiv
complaining about
\analyzecurrentreference
being unknown… Whent the typesetting stops because of this command,
saying « run » or rather « r » continues the typesetting.
How
Am 24.07.2014 um 14:03 schrieb Otared Kavian :
> Hi,
>
> Thanks for your attention, Wolfgang: indeed removing
> \analyzecurrentreference
> from your example allows mkiv to typeset correctly and obtain the expected
> result.
>
> Regarding Marco Patzer’s smartref command, I can typest the
Hi,
Thanks for your attention, Wolfgang: indeed removing
\analyzecurrentreference
from your example allows mkiv to typeset correctly and obtain the expected
result.
Regarding Marco Patzer’s smartref command, I can typest the following example
if I \input directly
\input condi
Am 24.07.2014 um 13:26 schrieb luigi scarso :
>
>
>
> On Thu, Jul 24, 2014 at 1:20 PM, Otared Kavian wrote:
> Hi Rik,
>
> As a matter of fact the example given by Wolfgang works despite mkiv
> complaining about
> \analyzecurrentreference
> being unknown… Whent the typesetting stops be
Am 24.07.2014 um 13:20 schrieb Otared Kavian :
> Hi Rik,
>
> As a matter of fact the example given by Wolfgang works despite mkiv
> complaining about
> \analyzecurrentreference
> being unknown… Whent the typesetting stops because of this command, saying «
> run » or rather « r » continue
On Thu, Jul 24, 2014 at 1:20 PM, Otared Kavian wrote:
> Hi Rik,
>
> As a matter of fact the example given by Wolfgang works despite mkiv
> complaining about
> \analyzecurrentreference
> being unknown… Whent the typesetting stops because of this command, saying
> « run » or rather « r » continues
Hi Rik,
As a matter of fact the example given by Wolfgang works despite mkiv
complaining about
\analyzecurrentreference
being unknown… Whent the typesetting stops because of this command, saying «
run » or rather « r » continues the typesetting.
I didn’t send the example module of Marco
On 2014-07-23 14:01, Otared Kavian wrote:
In my ConTeXt archives I found the following example from a discussion
on the mailing list: Wolfgang S. gave an answer which may help you:
Best regards: OK
...some text elided...
one can set conditional texts but these are internal macros
(which can
Hi,
In my ConTeXt archives I found the following example from a discussion on the
mailing list: Wolfgang S. gave an answer which may help you:
Best regards: OK
%% begin test-ref.tex
%
%Am 16.01.2011 um 20:58 schrieb Robert Blackstone:
%
%Hi all,
%
%I wonder if it is already possible to per
Suppose I have this fragment:
is shown in \in{figure}[foo] on \at{page}[foo].
\placefigure
[]
[foo]
I would like to leave the fragment “on \at{page}[foo]” out of the text if the
figure ends up on the same page as the \at. Is that doable or is this a matter
of manual tweaking at
22 matches
Mail list logo
