On 2022-05-10 17:39, Gerben Wierda via ntg-context wrote:
Example. Call with
context —mode=FR
- Uncomment the first commented lines. Compilation fails because mode
FR is on so that works
But I get English anyway. Uncomment the second commented part and it
fails, but it should not because
Fix
> On 10 May 2022, at 22:41, Gerben Wierda via ntg-context
> wrote:
>
> I currently have:
>
> \startnotallmodes[FR,RU]% english is the default
> \enablemode[EN]
> \stopnotallmodes
> \startmode[EN]
> \setuplanguage[en][patterns={en}]
>
Example. Call with
context —mode=FR
- Uncomment the first commented lines. Compilation fails because mode FR is on
so that works
But I get English anyway. Uncomment the second commented part and it fails, but
it should not because mode=EN is not turned on.
%\startmode[FR]
% \BLURBONE
%
I currently have:
\startnotallmodes[FR,RU]% english is the default
\enablemode[EN]
\stopmode
\startmode[EN]
\setuplanguage[en][patterns={en}]
\setupexternalfigure[directory=../LMTX-Output/without-ids/en/ArchiMate 3.1
Metamodel ESv4]
\stopmode
\startmode[FR]
\setuplanguage[fr][patterns={en,fr}]
Don't know how if there's an automatic way, perhaps look into ctx processing
instructions.
Anyway you can use
--result=name
As you have to set quite a few options on the command line (modes, language)
you'll perhaps want to use a makefile anyway.
Von:
receiving incremental file list
./
ctan.lsr
document-2.htm
download-1.htm
download-2.htm
logo-ade.png
logo-cts.png
logo-pod.png
rss.xml
sent 1,492 bytes received 135,306 bytes 273,596.00 bytes/sec
total size is 456,808,110 speedup is 3,339.29
Thank you.
Is it possible to change the name of the resulting PDF file based on the
language and a mode?
So that with a command
context language=fr mode=simple file.tex
the result is in
file-simple-fr.pdf
and with
context language=ru mode=none file.tex (or no mode
Gerben Wierda via ntg-context schrieb am 10.05.2022 um 00:15:
What is the easiest way to have a ‘database’ of translations for
strings and maybe links?
I now have 4 languages and 2 versions so 8 documents, but I’d like to
have all translatable strings together so I can maintain these in a
Thanks Hans, works perfectly.
Sorry for the late reply. Still working on the template and got another
one. Again, sorry.
The journal is in two-column form and the title, authors, and addresses
are spanned to
the full width. Very common. But the title may acknowledge to some
fund(s) and
On Tue, 10 May 2022 00:15:30 +0200
Gerben Wierda via ntg-context wrote:
> What is the easiest way to have a ‘database’ of translations for
> strings and maybe links?
Here's an idea:
\usemodule [translate]
%% \mainlanguage [nl]
\assigntranslation [en=alpha, nl=beta]\to\TRfoo
\translateinput
Am 10.05.22 um 00:15 schrieb Gerben Wierda via ntg-context:
What is the easiest way to have a ‘database’ of translations for strings
and maybe links?
I now have 4 languages and 2 versions so 8 documents, but I’d like to
have all translatable strings together so I can maintain these in a
Thanks Hraban, Taco. It is very helpful to get these hints. I will work
through them calmly over the next day or so. Not sure why the spaces
disappeared in the message (1 età came out as 1età etc.). Probably
because I copy-pasted from the text editor but all spacing is correct in
the editor I
> On 10 May 2022, at 04:03, jbf via ntg-context wrote:
>
> Can anyone give me a hint as to what I might be doing wrong? I realise that
> usually these references call on page numbers or section numbers, but I don't
> want/need (or do I?) to use those. I simply the reader to be able to click
Hi Julian,
while I can’t help you with the real issue, a few hints:
* Look into the .tuc file for the references. Do you find differences
between working and not-working examples?
* Do the examples work if you take them out of your big document or if
you change the order?
* There are
14 matches
Mail list logo
