- Hello word
What would you cover? Project structure? Style creation?
In my experience, most participants will know LaTeX, i.e. you must
tell them to forget everything they believe to know about TeX ;P
Oh, and don’t tell them that ConTeXt LMTX is much, much faster than any
LaTeX, because that’s
Am 09.07.22 um 19:27 schrieb Henning Hraban Ramm via ntg-context:
Am 09.07.22 um 17:48 schrieb juh+ntg-context--- via ntg-context:
My workshop was accepted. What shall I cover? It's a workshop for
beginners?
- Installation
- Hello word
What would you cover? Project structure? Style creation
Am 09.07.22 um 17:48 schrieb juh+ntg-context--- via ntg-context:
My workshop was accepted. What shall I cover? It's a workshop for
beginners?
- Installation
- Hello word
What would you cover? Project structure? Style creation?
In my experience, most participants will know LaTeX, i.e. you must
were extended.
I'll keep you updated.
My workshop was accepted. What shall I cover? It's a workshop for beginners?
- Installation
- Hello word
What would you cover? Project structure? Style creation?
I think one part will be: Where to find documentation?
Any hints appreciated.
And if you
his
necessary? For some reason, \btx_sbl_doifendswithpunctelse is not
recognized within the footnote environment...
\def\currentbtxcitealternative{footnote}
\def\currentbtxcategory{\btxfield{category}}
\def\currentbtxloctext{\btxparameter{loctext}}
\def\currentbtxaltloctext{\btxparameter{altloctex
teraction[state=start]
\starttext
superior typographic output \cite[lefttext={e.g.}][taraborelli:beauty].
Therefore, the {\TEX}book mentions that the word
\quotation{shel\noligature{ff}ul} should indeed be rendered without the
ff-ligature \cite[righttext={p.~19}][knuth:texbook].
\placelis
I am writing a document in Spanish and I notice that the syllable
partitioning of words does not conform to the rules of the language. And
so, for example, the word "limitarse" is partitioned as "lim-itarse"
(the correct one is "li-mi-tar-se"), "colores&quo
I am writing a document in Spanish and I notice that the syllable
partitioning of words does not conform to the rules of the language. And
so, for example, the word "limitarse" is partitioned as "lim-itarse"
(the correct one is "li-mi-tar-se"), "colores&quo
ated the files on Drive. Please see line
>> > 19, the last word "and". It is clearly out of alignment with the gid.
>> > I tested the alignment in MP and it should work, ie 2 characters are
>> > indeed one grid cell (semms from the fact that IBM Plex Mono was
y much Wolfgang! But, there is still something weird
> > going on with the font. I updated the files on Drive. Please see line
> > 19, the last word "and". It is clearly out of alignment with the gid.
> > I tested the alignment in MP and it should work, ie 2 characte
Stefan Nedeljkovic schrieb am 07.06.2022 um 07:25:
Thank you very much Wolfgang! But, there is still something weird
going on with the font. I updated the files on Drive. Please see line
19, the last word "and". It is clearly out of alignment with the gid.
I tested the align
ang! But, there is still something weird going on
> with the font. I updated the files on Drive. Please see line 19, the last
> word "and". It is clearly out of alignment with the gid. I tested the
> alignment in MP and it should work, ie 2 characters are indeed one grid
> cell (semms from th
A somewhat more complete testfile with a couple of options is below. My context
installation is not current so please double check, but I think it boils down
to this: apostrophes seem not to be considered to be part of a word. Once I
enable wolfin under \startlanguageoptions[en
Thank you very much Wolfgang! But, there is still something weird going on
with the font. I updated the files on Drive. Please see line 19, the last
word "and". It is clearly out of alignment with the gid. I tested the
alignment in MP and it should work, ie 2 characters are indeed one
Here's a short example (version 2022.05.11 11:36):
\setuplanguage[en][goodies={lang-en.llg}]
\starttext
% Expected: no ligature; actual: as expected
wolfish
% Expected: no ligatures; actual: ligature
wolfing
wolfin'
wolfin’
\stoptext
-context] Contractions in ligature suppression word list
Thanks for the response, Bruce.
1) The file you attached doesn't include the word "wolfing", nor "wolfin". I
assume they need to be
The suffixes section accounts for this. Wolfing and wolfish both suppress the
li
Thanks for the response, Bruce.
1) The file you attached doesn't include the word "wolfing", nor "wolfin".
> I assume they need to be
The suffixes section accounts for this. Wolfing and wolfish both suppress
the ligature correctly.
I removed the comma separators, go
n’,
> ing
> ]],
>
> See https://wiki.contextgarden.net/Ligatures#Word_suppression for an example
> usage.
>
> Thank you!
>
I'm probably missing something here but...
1) The file you attached doesn't include the word "wolfing", nor "wolfin". I
a
Attached are tweaked endings for words like "wolf" to include contracted
endings, but they are being ignored. This makes for a minor inconsistency:
wolfing -- no ligature
wolfish -- no ligature
wolfin -- no ligature (incorrect spelling, though)
wolfin' -- ligature
Any ideas? I tried
]\tablewordis{%
\NC \NC \NC\NR
\NC #1 \NC #2 \NC\NR
}
...then placing that in test2.tex, e.g.:
\tablewordis{my word}{my definition}
I get the error: " The file ended when scanning an argument."
Before the update, this code worked fine.
How can I \input a file while inside a table en
\NC \NC \NC\NR
> \NC #1 \NC #2 \NC\NR
> }
>
> ...then placing that in test2.tex, e.g.:
>
> \tablewordis{my word}{my definition}
>
> I get the error: " The file ended when scanning an argument."
>
> Before the update, this code worked fi
macro earlier in the document...
\define[2]\tablewordis{%
\NC \NC \NC\NR
\NC #1 \NC #2 \NC\NR
}
...then placing that in test2.tex, e.g.:
\tablewordis{my word}{my definition}
I get the error: " The file ended when scanning an argument."
Before the update, this code worked fine.
How ca
est2.tex, e.g.:
\tablewordis{my word}{my definition}
I get the error: " The file ended when scanning an argument."
Before the update, this code worked fine.
How can I \input a file while inside a table environment, as above?
I have a document that has 100s of these inputs in m
the Board of a journal to consider ConTeXt as
an additional option.
I want to make a module before I say anything. Right now I have this
title problem.
The journal requires the titles to be CAPITALISED, except for the
acronyms. I'm currently
using backticks`...`to wrap it and replace it with\egroup
for the
acronyms. I'm currently
using backticks`...`to wrap it and replace it with\egroup
...\WORD\bgroup{} with
lpeg. This kinda works, but that's so ugly. Besides, the actual story is
that I also want to
add markdown as an option, so the backticks actually have meanings.
I also checked thetypo
`...` to wrap it and replace it with \egroup ...\WORD\bgroup{}
with
lpeg. This kinda works, but that's so ugly. Besides, the actual story is that I
also want to
add markdown as an option, so the backticks actually have meanings.
I also checked the typo-cap.lua file to get a clue. But I used to use TeX
> \definetypeface[garamond]
> [mm][math][modern][default]
> \stoptypescript
>
> \starttext
>
> This is regular text.
>
> {\smallcaps This should be in smallcaps.}
>
> {\WORD This should be regular text, but capitalized, not really
> sma
be in smallcaps.}
{\WORD This should be regular text, but capitalized, not really
smallcaps.}
\stoptext
SerifCaps etc. works with the traditional \sc, don’t know about \smallcaps.
Are you sure your fonts are found?
mtxrun --script fonts --list --all --pattern=EBGaramond
If your regular OpenType
] [ss][sans][garamond][default]
\definetypeface[garamond] [mm][math][modern][default]
\stoptypescript
\starttext
This is regular text.
{\smallcaps This should be in smallcaps.}
{\WORD This should be regular text, but capitalized, not really smallcaps
Term} \NC {\bf Definition} \NC\NR".
I also tried defining a macro earlier in the document...
\define[2]\tablewordis{%
\NC \NC \NC\NR
\NC #1 \NC #2 \NC\NR
}
...then placing that in test2.tex, e.g.:
\tablewordis{my word}{my definition}
I get the error: " The file ended when scann
> On 18 Apr 2022, at 22:10, Wolfgang Schuster via ntg-context
> wrote:
>
> Bruce Horrocks via ntg-context schrieb am 18.04.2022 um 22:46:
>> In the MWE below the 'part' title is centred but on one line only and,
>> because it is a long title, the beginning and end are lost off the sides of
he workbook activity "Activity B".
The problem comes in that some activities have varied versions. Just as an
example, "Activity C might be a crossword puzzle in some chapters, but a word
search in other chapters. My poor solution has been to use registercyclist:
\define\altCa{pri
On Mon, 18 Apr 2022, Wolfgang Schuster via ntg-context wrote:
> Bruce Horrocks via ntg-context schrieb am 18.04.2022 um 22:46:
> > In the MWE below the 'part' title is centred but on one line only and,
> because it is a long title, the beginning and end are lost off the sides of
> the page.
> >
>
Bruce Horrocks via ntg-context schrieb am 18.04.2022 um 22:46:
In the MWE below the 'part' title is centred but on one line only and, because
it is a long title, the beginning and end are lost off the sides of the page.
If it were a 'chapter' title then I could insert '\\' to cause a line
In the MWE below the 'part' title is centred but on one line only and, because
it is a long title, the beginning and end are lost off the sides of the page.
If it were a 'chapter' title then I could insert '\\' to cause a line break at
that point. However this does not seem to work for 'part'.
ce Horrocks
> Hampshire, UK
>
>
>
> --
>
> Message: 4
> Date: Wed, 13 Apr 2022 07:37:58 +0530
> From: śrīrāma
> To: mailing list for ConTeXt users , A A
>
> Subject: Re: [NTG-context] Proper formatting
s to use \citem (comma item) and \pitem (period
> item) as required.
cleaned up the example –
%% start example
\def\citem{\item\AfterPar{\hspace[-normal],}\GetPar}
\def\pitem{\item\AfterPar{\hspace[-normal].}\GetPar}
\defineitemgroup
[pitemize]
[command=\Word]
\starttext
al].}\GetPar}
\defineitemgroup
[pitemize]
[command=\Word,numberconversion=words]
\starttext
\startpitemize[n]
\citem first item
\citem second item
\citem third item
\pitem fourth item
\stoppitemize
\stoptext
xample
\defineitemgroup
[pitemize]
[command=\Word]
\define\citem{%
\incrementnumber[itemgroup:pitemize]%
\sym{\symbol[\currentitemgroupsymbol]}%
\groupedcommand{}{,}%
}
\define\pitem{%
\incrementnumber[itemgroup:pitemize]%
\sym{\symbol[\currentitemgroupsymbol]}%
>
> post
> suggests using *\loadspellchecklist. *However, on of the arguments to
> this command includes a text file listing - and brace yourself - *all of
> the correctly spelled words*. I find this both an amusing and tragic
> proposition, since I basically need to spellcheck ba
rectly spelled words.
I find this both an amusing and tragic proposition, since I
basically need to spellcheck based on every word in a
given language.
What options are out there for someone who would like to do
s
- *all of the
correctly spelled words*. I find this both an amusing and tragic
proposition, since I basically need to spellcheck based on *every word in a
given language.*
What options are out there for someone who would like to do serious
spellchecking using ConTeXt on Windows platform, using Powershell
_1 \NC b_1 \NC c_1 \NR
>>> \NC a_2 \NC b_2 \NC c_2 \NR
>>> \NC a_3 \NC b_3 \NC c_3 \NR
>>> \stopxıɹʇɐɯ
>>> \stopformula
>>> for rotation matrices. This was demanded for some advanced math
>>> courses that Mikael teaches. It might inspire users to
suits their own obscure but nevertheless interesting
> > math.
> > At some point we realized that, with (also) scientific publishers
> > (of math journals) moving to MS Word and Indesign, we operate in a
> > rather peculiar niche and the fact that we use an upgraded and more
users to come up with demands that
suits their own obscure but nevertheless interesting math.
At some point we realized that, with (also) scientific publishers (of
math journals) moving to MS Word and Indesign, we operate in a rather
peculiar niche and the fact that we use an upgraded and more
users to come up with demands that
suits their own obscure but nevertheless interesting math.
At some point we realized that, with (also) scientific publishers (of
math journals) moving to MS Word and Indesign, we operate in a rather
peculiar niche and the fact that we use an upgraded and more
Am 16.03.22 um 16:48 schrieb Willi Egger via ntg-context:
Hi,
at the moment I am dealing with a German text. Although I have
\mainlanguage[de] in the preamble the word 'des Eiweißes' is hyphenated as 'des
Eiwei-ßes'. Of course this should be 'des Eiweis-ses'.
How can I make sure that ConTeXt
ntext wrote:
Hi,
at the moment I am dealing with a German text. Although I have
\mainlanguage[de] in the preamble the word 'des Eiweißes' is hyphenated as 'des
Eiwei-ßes'. Of course this should be 'des Eiweis-ses'.
How can I make sure that ConTeXt is hyphenating this corerctly?
Kind regards
On 3/16/2022 4:48 PM, Willi Egger via ntg-context wrote:
Hi,
at the moment I am dealing with a German text. Although I have
\mainlanguage[de] in the preamble the word 'des Eiweißes' is hyphenated as 'des
Eiwei-ßes'. Of course this should be 'des Eiweis-ses'.
How can I make sure that ConTeXt
Hi,
at the moment I am dealing with a German text. Although I have
\mainlanguage[de] in the preamble the word 'des Eiweißes' is hyphenated as 'des
Eiwei-ßes'. Of course this should be 'des Eiweis-ses'.
How can I make sure that ConTeXt is hyphenating this corerctly?
Kind regards
Willi
artchapter[title={Chapter \convertnumber{word}{\recurselevel}}]
\input knuth
\ifnum\headnumber[chapter]=5
{\bfd five}
\fi
\blank
\input tufte
\blank
\input ward
\blank
\ifnum\recurselevel=5
\page
\input zapf
uphead
[chapter]
[page=yes,
before=\directsetup{chapter:before},
aftersection=\directsetup{chapter:after}]
\starttext
\dorecurse{10}{
\startchapter[title={Chapter \convertnumber{word}{\recurselevel}}]
\input knuth
\ifnum\headnumber[chapter]=5
{\
{
\startchapter[title={Chapter \convertnumber{word}{\recurselevel}}]
\input knuth
\ifnum\headnumber[chapter]=5
{\bfd five}
\fi
\blank
\input tufte
\blank
\input ward
\blank
\ifnum\recurselevel=5
\page
\input zapf
stopsetups
\setuphead
[chapter]
[page=yes,
before=\directsetup{chapter:before},
aftersection=\directsetup{chapter:after}]
\starttext
\dorecurse{10}{
\startchapter[title={Chapter \convertnumber{word}{\recurselevel}}]
\input knuth
\blank
\i
ter[title={Chapter \convertnumber{word}{\recurselevel}}]
\input knuth
\blank
\input tufte
\blank
\input ward
\blank
\ifnum\recurselevel=5
\page
\input zapf
\input zapf
\fi
\stopchapter
}
\stoptext
%%% EOF
s chapter:after
\doifoddpageelse{}
{\page[empty]}
\stopsetups
\setuphead
[chapter]
[page=yes,
before=\directsetup{chapter:before},
aftersection=\directsetup{chapter:after}]
\starttext
\dorecurse{10}{
\startchapter[title={Chapter \convertnumber{word}{\recurselevel}}]
t;foo"] = "oof"
and such and there is in the next version also an exception mechanism
that permits clone a transliteration and add exceptions
There is another issue if one wants to use a dropcap and the rest of
that first word, and several following words are to be ty
for Serbian cyrillic and latin.
There is another issue if one wants to use a dropcap and the rest of
that first word, and several following words are to be typeset in small
caps.
If that first letter is Љ (or other two letters that transliterate as
digraphs), then the second letter of the digraph
in every instance?
\setupregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD]
\defineprocessor[special][style=italic]
\starttext
P\index[Plenary+periti]{Plenary Council+{\it periti} (experts)}
B\index[Plenary+beriti]{Plenary Council+{\it beriti} (experts)}
A\index[Plenary+aeriti]{Plenary Council
nstances,
> 40 or more in some cases). However, I did not ask for a 'simple' solution,
> just a solution! Thank you.
>
> Julian
>
> On 1/2/22 11:09, Adam Reviczky wrote:
>> Hi Julian,
>>
>> How about using the keys in every instance?
>>
>&g
Reviczky wrote:
Hi Julian,
How about using the keys in every instance?
\setupregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD]
\defineprocessor[special][style=italic]
\starttext
P\index[Plenary+periti]{Plenary Council+{\it periti} (experts)}
B\index[Plenary+beriti]{Plenary Council+{\it beriti
Hi Julian,
How about using the keys in every instance?
\setupregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD]
\defineprocessor[special][style=italic]
\starttext
P\index[Plenary+periti]{Plenary Council+{\it periti} (experts)}
B\index[Plenary+beriti]{Plenary Council+{\it beriti} (experts
. The processor is not
for the 'periti' case above but I use it for book titles.
\setupregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD]
\defineprocessor[special][style=italic]
In the periti case it is the \it command that clearly interferes with
correct alphabetic positioning in the sub entry
with the subentry
surrounded by single quotes. It too comes first in the list if I use a
double key. So clearly it is the fact that there is formatting ({\it
something}) or quotes ({‘word’}) in a subentry that causes the problem,
and I am wondering how to overcome this.
Julian
On 30/1/22 20:59, Hans
list in three columns. The problem is, if there
> is an item with a somewhat long description, it can be split across columns.
> See the example below:
>
> \starttext
> \startcolumns[n=3]%
> \startitemize[1]%
> \item pizza cutter
>
be split across columns. See the
example below:
\starttext \startcolumns[n=3]% \startitemize[1]% \item
pizza cutter \item a word processor (or notebook paper)
\stopitemize% \stopcolumns%\stoptext
In the example, it split the second item across
Hi Julian,
Have you tried \index[Innovative]{‘Innovative’}?
See wiki entry: https://wiki.contextgarden.net/Registers
- To sort a word (such as "ConTeXt" under "C"), use: \index
<https://wiki.contextgarden.net/Command/index>[CONTEXT]{\ConTeXt}
You would have to cha
Afghanistan (in Iran a
> parasang is 6 kilometers now).
(Personnaly I think the Roman mile has its origin in the Persian « mil »: I
> think the etymology of the word mile based on the word « mille », a
> thousand, cannot be correct since it does not correspond to one thousand of
>
On 1/26/2022 10:07 PM, jbf via ntg-context wrote:
Just be careful, though (writing as a native English speaker), because
the word 'polymath' for English speaker is not a reference to
mathematicians at all. (Greek/mathē/ means 'learning' not mathematics).
Translators are well aware
Just be careful, though (writing as a native English speaker), because
the word 'polymath' for English speaker is not a reference to
mathematicians at all. (Greek/mathē/ means 'learning' not mathematics).
Translators are well aware of the danger of homonyms, and if you go for
a title like
think the
etymology of the word mile based on the word « mille », a thousand, cannot be
correct since it does not correspond to one thousand of any other unit of
length used in the Roman empire).
Best regards: Otared
the Persian empire, and are still used, in particular the parasang, in
Iran and Afghanistan (in Iran a parasang is 6 kilometers now). (Personnaly I
think the Roman mile has its origin in the Persian « mil »: I think the
etymology of the word mile based on the word « mille », a thousand, cannot be
c
\stopcolumns
%word search clues (should be simple, but strangely this keeps getting the ☞
logo added instead of showing numbers)
\startitemize[n]
\item a type of hat worn
\item a cold season
\stopitemize
___
If your
Joey sent me and it won't populate
`\placenotes[footnote]` with any content:
\startbuffer [bib]
@Book{clark1989,
author = {Clark, William},
title = {Railroads \word{and} railroad towns \word{in} New Mexico},
publisher = {New Mexico Magazine},
year = {1989},
address = {Albuquerque, New Mexico
> On 23 Jan 2022, at 21:40, Joel via ntg-context wrote:
>
> I am adding items to an index simply using `\index{word}`.
>
> There are a few cases where instead of printing just the page number where
> `\index{word}` is placed, I need the entire page range for that chapter
Am 23.01.22 um 22:40 schrieb Joel via ntg-context:
I am adding items to an index simply using `\index{word}`.
There are a few cases where instead of printing just the page number
where `\index{word}` is placed, I need the entire page range for that
chapter to be displayed. For instance
I am adding items to an index simply using `\index{word}`.
There are a few cases where instead of printing just the page number where
`\index{word}` is placed, I need the entire page range for that chapter to be
displayed. For instance, if Chapter 3 spans page 22-50, and I place
`\index{word
I've avoided forcing capitalization in too many places in the SBL rendering
because there are often language-specific (or, within English, even
dialect-specific) differences regarding what should be capitalized. I think
I already enforce capitalization of the first word, though
of the words that should not be capitalized
in my BiBTeX file as with \word{of} so they will ignore any instructions to
become capitalized.
--Joel
___
If your question is of interest to others as well, please add
ersions; kauśika is working on
> >
> > Perhaps the following notes are useful.
> >
> > 1. The simplest way, and what I was talking about, is to write and print
> > Sanskrit in
> > transliteration.
> >
> > ānandaḥ -> ānandaḥ
> >
>
, is to write and print
Sanskrit in
transliteration.
ānandaḥ -> ānandaḥ
2. Then we can of course write and print the same word in the usual
Indian Script (Devanāgarī)
आनन्दः -> आनन्दः
3. But for academic use, one wants an input in roman (e-text are usually
in roman), and the
-> ānandaḥ
2. Then we can of course write and print the same word in the usual
Indian Script (Devanāgarī)
आनन्दः -> आनन्दः
3. But for academic use, one wants an input in roman (e-text are
usually in roman), and the option
to have an output in Devanāgarī)
ānandaḥ ->
On 1/9/2022 11:23 AM, hanneder--- via ntg-context wrote:
1. In Sanskrit prose it is possible to produce compounds that span a few
lines. The concept of
"word" or "word division" fails here, as are the TeX mechanisms.
What we need in practice would be a "hyph
a few
lines. The concept of
"word" or "word division" fails here, as are the TeX mechanisms.
What we need in practice would be a "hyphenation" for the language
Sanskrit that hyphenates
after all Sanskrit vowels (in transcription this would be a, ā,
at
> user-unfriendly (my technical knowledge is rather limited).
>
>
> Dear Hans,
>
> two recurring problems are rather specifically Indological and they concern
> hyphenation and
> font.
>
> 1. In Sanskrit prose it is possible to produce compounds that span a few
&
-context@ntg.nl> het volgende geschreven:
> >
> > I was just writing a mail (below) and saw:
> >
> >> They do indic scripts and Kai made the first version of the devanagari
> code for the context fontloader code that I then optimized.
> >
> > Fasci
On Sun, Jan 09, 2022 at 11:46:44PM +0100, Hans Hagen via ntg-context wrote:
> On 1/9/2022 11:23 AM, hanneder--- via ntg-context wrote:
>> 1. In Sanskrit prose it is possible to produce compounds that span a few
>> lines. The concept of
>> "word" or "word
learn more about that or is that
> user-unfriendly (my technical knowledge is rather limited).
>
>
> Dear Hans,
>
> two recurring problems are rather specifically Indological and they concern
> hyphenation and
> font.
>
> 1. In Sanskrit prose it is possible to produc
On 1/9/2022 11:23 AM, hanneder--- via ntg-context wrote:
1. In Sanskrit prose it is possible to produce compounds that span a few
lines. The concept of
"word" or "word division" fails here, as are the TeX mechanisms.
What we need in practice would be a "hyph
] [page=no]
\startdocument [title={Dummy title}]
\dorecurse{5}
{\startchapter[title={Chapter \convertnumber{word}{#1}}]
\samplefile{lorem}
\stopchapter}
\stopdocument
Wolfgang
___
If your question
fontloader code that I then optimized.
> >
> > Fascinating. Where can I learn more about that or is that
> > user-unfriendly (my technical knowledge is rather limited).
> >
> >
> > Dear Hans,
> >
> > two recurring problems are rather specifically Indolo
n and
> font.
>
> 1. In Sanskrit prose it is possible to produce compounds that span a few
> lines. The concept of
> "word" or "word division" fails here, as are the TeX mechanisms.
>
> What we need in practice would be a "hyphenation" for the lang
).
Dear Hans,
two recurring problems are rather specifically Indological and they
concern hyphenation and
font.
1. In Sanskrit prose it is possible to produce compounds that span a
few lines. The concept of
"word" or "word division" fails here, as are the TeX mechanis
gt;
>
>
> On Fri, Jan 7, 2022 at 6:25 PM hanneder--- via ntg-context <
> ntg-context@ntg.nl> wrote:
>
>>
>> Probably the situation in South Asian Studies (Indology) is peculiar.
>> As I indicated, there are mostly no budgets for book typesetting in
>&
peculiar.
As I indicated, there are mostly no budgets for book typesetting in
Indology and
I know of no real expert for typesetting in this field. In other
words, the authors
have do it themselves, usually in Word etc., but some do use TeX etc.
Our publications
series (Indo
have do it themselves, usually in Word etc., but some do use TeX etc.
Our publications
series (Indologica Marpurgensia) is, for instance, all done with LaTeX,
as are my publications
with Harrassowitz, which is the largest publisher in our field in
Germany. There is no institution
offering
xpert for typesetting in this field. In other
> words, the authors
> have do it themselves, usually in Word etc., but some do use TeX etc.
> Our publications
> series (Indologica Marpurgensia) is, for instance, all done with
> LaTeX, as are my publications
> with Harrassowitz, whic
Probably the situation in South Asian Studies (Indology) is peculiar.
As I indicated, there are mostly no budgets for book typesetting in
Indology and
I know of no real expert for typesetting in this field. In other
words, the authors
have do it themselves, usually in Word etc., but some do
workflow,
otherwise Word-based (->XML->LaTeX or ->InDesign). Of course they accept
all kind of data; it looks like they’re really good in automated workflows.
But I guess there are strong competitors in the far east..
. Almost all publishers still expect a Word
file, so the tool of choice is pandoc to downgrade from TeX to docx.
Sorry to end on this depressing note.
Word documents for critical editions? In that case, publishers will have
to typeset the book themselves, won’t they?
As far as I know, some
101 - 200 of 3045 matches
Mail list logo
