On 22-10-2010 4:08, seasoul wrote:
Is there a way to justify the line? I mean no word hyphenation, and words
\setupalign[nothyphenated]
are justified like in office word. My boss is quite angry to see
hyphenations at the end of lines in my file.
lucky him that he was not born in Germany
created by ConTeXt is \jobname.words: so
\typefile{words-003.words}
should be
\typefile{\jobname.words}
as indicated in lang-wrd.mkiv.
sure, although it can be another name as well .. btw, I added a shower
as well
\usemodule[s-lan-03]
\starttext
\setupspellchecking[state=start,method=2
knuth \blank
\setupspellchecking[list=ward] \input ward \blank
\typefile{words-003.words}
\stoptext
I uploaded a beta zip that has it so it will end up in the minimals.
Hans
-
Hans Hagen
question is: can one have both the upper frame turned on at the begining
of the highlighted text (and only there) and also the bottom frame turned on at
the end (and only there).
In other words, a highlighted framed text spanning over two (or more) pages,
would be like a big rectangle of which the upper
the bottom frame is turned on (of course this is what we want).
So my question is: can one have both the upper frame turned on at the
begining of the highlighted text (and only there) and also the bottom frame
turned on at the end (and only there).
In other words, a highlighted framed text
on (of course this is what we want).
So my question is: can one have both the upper frame turned on at the
begining of the highlighted text (and only there) and also the bottom frame
turned on at the end (and only there).
In other words, a highlighted framed text spanning over two (or more) pages,
would
Here is a simple section header. It runs way out of the margin. Any idea why?
I do not want hyphenation. Words that run over the boundary should be skipped
to the next line down. Why does it not do that here?
Also note that if i change flushleft to middle, it works fine (except that
i
don't
On 14-10-2010 7:59, Brian Wedde wrote:
Here is a simple section header. It runs way out of the margin. Any idea why?
I do not want hyphenation. Words that run over the boundary should be skipped
to the next line down. Why does it not do that here?
Also note that if i change flushleft to middle
was trying to say. In practice, hardly anyone will want an
individual index for Spanish if they have just two Spanish words in an English
book. And someone (me) might say that they want three Greek terms in their
German index at logical places.
Some time ago I made an lpeg from the bnf in [1
On 2010-10-05 15:29:38, Thomas A. Schmitz wrote:
And someone (me) might
say that they want three Greek terms in their German index at
logical places.
Try the definitions in the attachment. For three words only they
will be fine. But if the count
shelf. Most English books
have a separate index for Greek terms; when they sort Greek terms with English
words, they use transliteration. The problem with polytonic Greek is that so
many different unicode characters need to have the same sort entry. If I ever
see the necessity of setting this up
Hi list,
I wrote a custom pretty printer (verbatim) for Free Pascal/Turbo
Pascal/Delphi source files. It's attached to this mail together with a
ConTeXt test files that shows the features and some special cases.
The pretty printer can handle:
reserved words (bold
of 1000 (max. 131072)
1 words of extra memory for PDF output out of 1 (max. 1000)
--
Best regards,
Li Yanrui (李延瑞)
___
If your question is of interest to others as well, please add an entry to the
Wiki
Hi folks.
Just hit a strange feature using \about to give me the title of a
referenced section. When the title is long, there seems to be an
automatic cut-off, as if some form of \nomarking had been used on the
last words of the title. So with a section somewhere in the text like
\section
Am 15.09.2010 um 09:22 schrieb Duncan Hothersall:
Hi folks.
Just hit a strange feature using \about to give me the title of a referenced
section. When the title is long, there seems to be an automatic cut-off, as
if some form of \nomarking had been used on the last words of the title. So
$. Then for all null-homotopic words $u, v$ in
${\cal P}$,
\setupitems[align=right]
\startitemize[r][left=(,right=),stopper=]
\item $\text{area}(u \cdot w) = \text{area}
(w \cdot u)$
\item $\text{area}(wuw^{-1}) = \text{area}(w)$
\item $\text{area}(u \cdot w) \leq \text{area}(u) + \text{area}(w)$
\item $\text
$. Then for all null-homotopic words $u, v$ in
${\cal P}$,
\setupitems[align=right]
\startitemize[r][left=(,right=),stopper=]
\item $\text{area}(u \cdot w) = \text{area}
(w \cdot u)$
\item $\text{area}(wuw^{-1}) = \text{area}(w)$
\item $\text{area}(u \cdot w) \leq \text{area}(u) + \text{area}(w)$
\item $\text
$. Then for all null-homotopic words $u, v$ in
${\cal P}$,
\setupitems[align=right]
\startitemize[r][left=(,right=),stopper=]
\item $\text{area}(u \cdot w) = \text{area}
(w \cdot u)$
\item $\text{area}(wuw^{-1}) = \text{area}(w)$
\item $\text{area}(u \cdot w) \leq \text{area}(u) + \text{area}(w)$
\item
$. Then for all null-homotopic words $u, v$ in
${\cal P}$,
\setupitems[align=right]
\startitemize[r][left=(,right=),stopper=]
\item $\text{area}(u \cdot w) = \text{area}
(w \cdot u)$
\item $\text{area}(wuw^{-1}) = \text{area}(w)$
\item $\text{area}(u \cdot w) \leq \text{area}(u) + \text{area}(w)$
\item $\text
: cont-err loaded
(/usr/share/texmf/tex/context/base/cont-err.tex
systems : no file 'cont-sys.tex', using 'cont-sys.rme' instead
) )
Here is how much of TeX's memory you used:
2649 strings out of 457152
48998 string characters out of 2542702
4759818 words of memory out of 7690716
42414
=on,
framecolor=mycolor2]
but I remember that there used to be a command that allowed doing the
same, but spanning the text over multiple pages. I would be grateful
for any hint/pointer to the manual. I've found a document that does
underlining of words in paragraphs, but this seems like an easier
problem
.
\looseness=-1 is not enough. I also tried inserting discretional hyphens where
they can be more usefull, some times helps me but not now.
How can I FORCE spacing bettween characters, words (or both). I don't care if
it looks too tight.
I know that this can seems sacrilegious, but nobody will notice
--sorters.sort(dwwords, sorters.comparers.basic)
sorters.sort(dwwords, sorters.comparers.polish)
end
function document.whatever.flushtext()
local words = document.whatever.words
local previous = false
local p_word = false
for i=1, #words do
local word = words[i]
local
to write a simple text but shouldn't it be possible to give a few opening and also closing words for the letter, because the reader should know for whom the content is.
+You saw in the last example how to write a simple text. But shouldn’t it be possible to give a few opening and also closing words
look at pret-*.lua: there is a visualizer.flush_line in there that
can write to a file, apply vim, and read in the result (can also be
words instead of lines).
Hans
-
Hans Hagen | PRAGMA ADE
footnotes of a document shall be placed in the
right margin rather than below the main text area. Additionally, though,
the footnotes should not be placed near the call up (similar to what
\marginpar does), but type set en bloc at the bottom of the page. In
other words, the main text area should have
(/opt/tl/2009/texmf-dist/tex/context/base/cont-err.tex
systems : no file 'cont-sys.tex', using 'cont-sys.rme' instead
) )
Here is how much of TeX's memory you used:
1045 strings out of 457152
16610 string characters out of 2541996
4687853 words of memory out of 7118750
40822 multiletter
not extremely happy
because of these terms, but it's not a real problem for me.
While I know Polacken as a derogatory word for Polish (or other
Eastern European) people, I never encountered polnische Wirtschaft.
Similar cuss words are Itzig for Jews (originally just a form of
Isaak), Molukker
personal point of view is that the so-called political correctness
is something I actively fight against, by means of NOT using they or
Afroamericans or other such strange inventions. These new words
somehow remind me of Orwell's 1984...
So what do you write instead? Negro?
And what's
in the
right margin rather than below the main text area. Additionally, though,
the footnotes should not be placed near the call up (similar to what
\marginpar does), but type set en bloc at the bottom of the page. In
other words, the main text area should have fixed margins all round
across all pages
...@atos.wmid.amu.edu.pl wrote:
Hi,
what an interesting discussion!
My personal point of view is that the so-called political correctness
is something I actively fight against, by means of NOT using they or
Afroamericans or other such strange inventions. These new words
somehow remind me of Orwell's 1984
direction.
In other words: I cannot imagine an experiment which might prove any of
us wrong on this subject, and I can see some hints which support your
claim and some which support mine.
Regards
--
Marcin Borkowski (http://mbork.pl
mb...@atos.wmid.amu.edu.pl wrote:
Hi,
what an interesting discussion!
My personal point of view is that the so-called political correctness
is something I actively fight against, by means of NOT using they or
Afroamericans or other such strange inventions. These new words
Hi!
Henning Hraban Ramm a écrit :
So, as several other posters already said: It's not the words who are to
blame, but the speakers and their mind sets...
Let me just add a comment about he/she and the willing of
the speakers.
In Esperanto, there is
li = he
ŝi = she (same pronunciation)
ĝi
by the
groups themselves, that is).
There are many cases in American culture at least of groups using a
term within themselves that they do not want others to use, but not
usually the names used by that population when politely referring to
themselves (i.e. generally these terms are loaded slang words
On 26-7-2010 11:36, Martin Althoff wrote:
\definebodyfont [10pt,11pt,12pt] [rm] [tfe=Serif at 48pt, ite=SerifItalic at
48pt]
\tfe Big {\it Words}.
What I simply don't understand is the need for multiple font size declarations. I can
(kind of) see that it might be necessary (looking
actively fight against, by means of NOT using they or
Afroamericans or other such strange inventions. These new words
somehow remind me of Orwell's 1984...
So what do you write instead? Negro?
And what's wrong with Negro? AFAIK, it means black, so it just
describes the reality. This is what
and
denying
the existence of the others.
We have the same issue in Polish. Until now I didn't know that the
Romowie vs Cyganie (in Polish) has also this kind of problem. This
particular example is even more interesting because of a few Polish
words, originating from the word Cyganie, like
is that the so-called political correctness
is something I actively fight against, by means of NOT using they or
Afroamericans or other such strange inventions. These new words
somehow remind me of Orwell's 1984...
So what do you write instead? Negro?
And what's wrong with Negro? AFAIK
at the example:
\definebodyfont [10pt,11pt,12pt] [rm] [tfe=Serif at 48pt, ite=SerifItalic at
48pt]
\tfe Big {\it Words}.
What I simply don't understand is the need for multiple font size declarations.
I can (kind of) see that it might be necessary (looking at typescripts), if the
whole typescript
Hi,
what an interesting discussion!
My personal point of view is that the so-called political correctness
is something I actively fight against, by means of NOT using they or
Afroamericans or other such strange inventions. These new words
somehow remind me of Orwell's 1984...
Regards
such strange inventions. These new words
somehow remind me of Orwell's 1984...
So what do you write instead? Negro?
'Political correctness' can be onerous, and often contradictory to my
anti-authoritarian nature, but in the end it is not the Man who
issues requests for language changes so much
I don't see how this applies: there are plenty of characters provided
by Unicode that can be used regardless of which language I am writing
in..
Yes, but they're symbols, not letters (nor ideographs or characters
from a syllabary, etc.); and they're even less words. Are you
suggesting we
actively fight against, by means of NOT using they or
Afroamericans or other such strange inventions. These new words
somehow remind me of Orwell's 1984...
So what do you write instead? Negro?
Personally I feel that the political correctness has gone a bit too far, but
where the line should
}\stopunderline{} posuere arcu.
Donec \startunderline{gravida}\stopunderline{} posuere arcu.
\stoptext
What I need is underlining that occurs at a fixed/constant distance below
the words underlined (allowing for descenders, of course, when they are
present).
Any suggestions?
just
the
words underlined (allowing for descenders, of course, when they are present).
Any suggestions?
Alan___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl
that occurs at a fixed/constant distance below the
words underlined (allowing for descenders, of course, when they are present).
Any suggestions?
just use \underbar(s)
-
Hans Hagen | PRAGMA
On Sun, Jul 11, 2010 at 00:21, Martin Schröder mar...@oneiros.de wrote:
2010/7/10 Mojca Miklavec mojca.miklavec.li...@gmail.com:
avoiding PDF for all costs makes sense or not. Expressed in other
words: what usually happens when one sends PDF to PostScript printer?
Does it print the document
On Sun, 11 Jul 2010, Martin Schr?der wrote:
2010/7/10 Mojca Miklavec mojca.miklavec.li...@gmail.com:
avoiding PDF for all costs makes sense or not. Expressed in other
words: what usually happens when one sends PDF to PostScript printer?
Does it print the document almost-natively
not sure if
avoiding PDF for all costs makes sense or not. Expressed in other
words: what usually happens when one sends PDF to PostScript printer?
Does it print the document almost-natively or not?
This page says:
http://www.adobe.com/print/features/psvspdf/
In order for a PDF file to be printed
2010/7/10 Mojca Miklavec mojca.miklavec.li...@gmail.com:
avoiding PDF for all costs makes sense or not. Expressed in other
words: what usually happens when one sends PDF to PostScript printer?
Does it print the document almost-natively or not?
Typically your viewer (e.g. Adobe Reader) or your
of them yet to get through my thick skull an
understanding of what they do and how to use them. Can you explain to me the
significance of the [1]s after the defines?
I would still like to be able to convert chapter numbers to words without
impacting the table of contents. I am confused about how
=\ChapterTextStretch,
deepnumbercommand=\ChapterNumberStretch]
\starttext
\chapter{Test Chapter Title}
\input knuth
\stoptext
Wolfgang
I've tried to modify this code to change the chapter numbers to words. That
part was successful but the above code only stretches the word Chapter but
not the numbers' words
a text
which is longer than, say, ten pages. In other words, a language which has
maximum compression would actually be completely unsuited to conveying
information beyond a certain degree of complexity, because you could never find
out whether a text is right or wrong. And this is a question
,Te
n,Eleven]
\setuphead[chapter]
[conversion=numstring]
How should i know you're using mkii! Replace \setuphead with \setupsection:
\setupsection[chapter][conversion=numstring]
Wolfgang
The following example converts chapter numbers to words for the \chapter
logic but also converts
in the text begin with the words rather than the numerals
(again, I prefer numerals for section numbers). The documentation probably
explains how to deal with this, but I haven't been able to find it. All I
want to do is make a cosmetic change to the tops of the chapter start pages.
Tom Benjey
717
]
\start
\setcharacterkerning[extra]
\hfill {\sc{\lowercased{\getmarking[section]}}}\hfill
\stop
\stopsetups
You can save a few lines (the second variant gives a bigger spaces):
\setupheadertexts[\WORDS{\tfx\kerncharacters[0.25]\getmarking[section]}]
%\setupheadertexts[{\setuptolerance
,
these wise words were written 1 1/2 years ago ... and publishers indeed more
and more often ask for that!
For me, the only way to do tagging is with AcrobatPro.
But as LuaTeX made so much progress in the last 18 month, maybe is there also
some break-through on this topic?
Steffen
a problem
for the moment, but it's clearly not the feature your printer asks
for,
and as a rule, you can be sure that if some functionality is essential
to publishers, it will be added quickly to ConTeXt :-)
Hi Hans,
these wise words were written 1 1/2 years ago ... and publishers
indeed more
, the following errors out:
Chapter \Word{\numstr{23}}
As does
Chapter \Words{\numstr{23}}
but
Chapter \numstr{23}
Works as does
Chapter \Words{twenty-three}
However, the former returns twenty-three (all lower case)
and the latter returns Twenty-three (only the first part is in upper case)
It's
, the following errors out:
Chapter \Word{\numstr{23}}
As does
Chapter \Words{\numstr{23}}
but
Chapter \numstr{23}
Works as does
Chapter \Words{twenty-three}
However, the former returns twenty-three (all lower case)
and the latter returns Twenty-three (only the first part is in upper
Hello,
I have two languages in my document: English and Russian, and want to
enable hyphenation for both. (By default, only English words are
hyphenated). How to achive this?
Rgrds,
Vyatcheslav
___
If your
On Fri, Jun 25, 2010 at 14:19, Vyatcheslav Yatskovsky wrote:
Hello,
I have two languages in my document: English and Russian, and want to enable
hyphenation for both. (By default, only English words are hyphenated). How
to achive this?
\mainlanguage[ru]
\starttext
some russian text
see the
command is defined with '\setvalue{\e!start\v!tablehead}' and the two
values \e!start and \v!tablehead are replaced with their dutch words
'start' and 'tabelkop'.
Wolfgang
___
If your question
On 25-6-2010 2:24, Mojca Miklavec wrote:
On Fri, Jun 25, 2010 at 14:19, Vyatcheslav Yatskovsky wrote:
Hello,
I have two languages in my document: English and Russian, and want to enable
hyphenation for both. (By default, only English words are hyphenated). How
to achive this?
\mainlanguage
Hi,
Please, I need urgent help with page numbering!
I begin my document with three standardmakeup pages, and expect fourth
(normal) one to have number 4. But it is 1, whatever I do. In
particular, \setuppagenumbering[number=4] has no effect.
In other words, I need numbering from the very
). If you speak these words aloud you will notice
that in spite of the consonants the sound is really very
well described. And what about a cow, does it say boe, mboe or mm?
\stopmarginrule
\stoptext
___
If your
),
couin||couin (French), gick||gack (German), rap||rap (Danish) and
mech||mech (Spanish). If you speak these words aloud you will notice
that in spite of the consonants the sound is really very
well described. And what about a cow, does it say boe, mboe or mm?
\stopmarginrule
\stoptext
A bug
Mojca Miklavec (2010-05-24 02:16):
Dear Claudio,
Thanks a lot for your prompt reply.
On Mon, May 24, 2010 at 00:39, Claudio Beccari wrote:
Dear Mojca,
no proper Italian word ends in ch (this digraph in normal Italian words is
pronunced as k, not as č or ć).
Nevertheless
Dear Claudio,
Thanks a lot for your prompt reply.
On Mon, May 24, 2010 at 00:39, Claudio Beccari wrote:
Dear Mojca,
no proper Italian word ends in ch (this digraph in normal Italian words is
pronunced as k, not as č or ć).
Nevertheless there are a number of surnames dating back to the old
. Problem I describe here,
can be seen on words under letter L.
new beta
And just one last question. I was playing with translation of user interface
(for my bachelor thesis) and I wasn't able to add a new one. I tried to put
some test translation in mult-def.lua and even modified mtx
\index{Árun}Árun
\index{žába}žába
\index{cibule}cibule
\index{čára}čára
\index{bomba}bomba
\index{Auto}Auto
\index{arek}arek
\placeindex
\stoptext
ConTeXt sorted only letters without accent and rest of the words just put
before index without any kind of sorting, also accented characters
{ámerika}ámerika
\index{arábie}arábie
\index{Árun}Árun
\index{žába}žába
\index{cibule}cibule
\index{čára}čára
\index{bomba}bomba
\index{Auto}Auto
\index{arek}arek
\placeindex
\stoptext
ConTeXt sorted only letters without accent and rest of the words just put
before index without any kind
\enabletrackers[sorters.tests]
just tracking
Thanks, it's working now, but still it sort some words bit different
compared to MkII. But it's ok for now, I will check czech norm and try to
fix it if needed.
Also I have question. In my bachelor thesis I'm describe language support
for ConTeXt
On 15-5-2010 8:14, Tomáš Pustelník wrote:
Thanks, it's working now, but still it sort some words bit different
compared to MkII. But it's ok for now, I will check czech norm and try
to fix it if needed.
we can support several norms if needed
Also I have question. In my bachelor thesis I'm
hours behind the website
you can fetch the beta from the website and unzip it in texmf-context and
then run luatools --generate
\enabletrackers[sorters.tests]
just tracking
Thanks, it's working now, but still it sort some words bit different compared
to MkII. But it's ok for now, I
sometimes be very inefficient.
ii) Is it still up-to-date?
Apart from a recently reported bug I don't know of any changes in
MkII, but maybe I should write a few words about MkIV.
iii) Why should I better use \sometxt?
What do you mean by »more reliable«? After having read your MyWay I
have slightly
different spacing
Something I find very annoying is variable interline spacing, if I've,
for example, a line with some Arabic words vocalized I get some times
too much white space above it that it almost looks like an empty line.
It makes the page look like crap. Is there a way
limitations (those 16 values of ht dp) we have slightly
different spacing
Something I find very annoying is variable interline spacing, if I've,
for example, a line with some Arabic words vocalized I get some times
too much white space above it that it almost looks like an empty line.
It makes the page look
relates to the ex height and as in mkiv we don't have
the tfm limitations (those 16 values of ht dp) we have slightly
different spacing
Something I find very annoying is variable interline spacing, if I've,
for example, a line with some Arabic words vocalized I get some times
too much white
relates to the ex height and as in mkiv we don't have
the tfm limitations (those 16 values of ht dp) we have slightly
different spacing
Something I find very annoying is variable interline spacing, if I've,
for example, a line with some Arabic words vocalized I get some times
too much white space
, if I've,
for example, a line with some Arabic words vocalized I get some times
too much white space above it that it almost looks like an empty line.
It makes the page look like crap. Is there a way to force fixed
interline spacing?
Can you give an example?
turn turn grid on .. but even
On Thu, 13 May 2010 15:06:09 -0500, Khaled Hosny khaledho...@eglug.org
wrote:
Something I find very annoying is variable interline spacing, if I've,
for example, a line with some Arabic words vocalized I get some times
too much white space above it that it almost looks like an empty line
.
\startcantresistmode
the lineheight relates to the ex height and as in mkiv we don't have
the tfm limitations (those 16 values of ht dp) we have slightly
different spacing
Something I find very annoying is variable interline spacing, if I've,
for example, a line with some Arabic words vocalized I get
. And two
hyphens (or an en-dash) is too large. I've never seen the advice in a
typography book to kern two hyphens. I don't know why this is
implemented like this.
because we needed it to be this way: we use it for separating compound
words and then we want to have the hyphen between the compounds
Marco wrote on Monday, May 10, 2010 7:27 AM:
1. || does *not* produce a en-dash but to kerned hyphens
You're right, I looked it up in the sources. It just looked like an
en-dash for me. But this is wrong. For hyphenation a hyphen is used.
The
font designer has created a dedicated glyph for
Hello,
\starttext
\startLUA
printbla -- words are transposed!
\stopLUA
\stoptext
Cheers, Peter
--
Contact information: http://pmrb.free.fr/contact/
___
If your question is of interest
On 10-5-2010 10:43, Peter Münster wrote:
\starttext
\startLUA
printbla-- words are transposed!
\stopLUA
\stoptext
in pret-lua.lua, line 265:
elseif c == '' or c == ' then
if word then
state = flush_lua_word(state,word)
word = nil
end
in a typography book to kern two hyphens. I don't
know why this is implemented like this.
because we needed it to be this way: we use it for separating
compound words and then we want to have the hyphen between the
compounds to be different from the ones within
That's not how it is done in everyday
It seems that the en-dash *can* be used in English in some cases:
'high-priority--high-pressure tasks' from
http://en.wikipedia.org/wiki/Hyphen
I see. But this is a --more or less-- contructed case where using an
en-dash instead of a hyphen makes sense. I agree with this example, the
en-dash
On 16-4-2010 4:46, Marco wrote:
Hi,
I've yet another hyphenation problem. I cannot get proper
hyphenation in composed words. Take this MWE:
a mix up of settings .. fized in next beta
Hi Hans,
the following code still produces an en dash instead of a hyphen.
\setuplayout [width=1.5cm
Am 09.05.10 21:34, schrieb Marco:
On 16-4-2010 4:46, Marco wrote:
Hi,
I've yet another hyphenation problem. I cannot get proper
hyphenation in composed words. Take this MWE:
a mix up of settings .. fized in next beta
Hi Hans,
the following code still produces an en dash
1. || does *not* produce a en-dash but to kerned hyphens
You're right, I looked it up in the sources. It just looked like an
en-dash for me. But this is wrong. For hyphenation a hyphen is used. The
font designer has created a dedicated glyph for this purpose. And two
hyphens (or an en-dash) is
of a
book that defines the specialized words and phrases that the book uses
that might not be known to the general reader. Here is a definition
of glossary:
Ach ja, gsub(manual,index,glossary) zal je niet geven wat je zoekt
vrees ik. Overigens, we hebben dat soort 'begrippenlijsten in vrijwel
elk
dictionary. (As defined by
M.~Saunders)%
}
\gloss{index}{%
An index (plural: indexes) is a list of words or phrases ('headings') and
associated pointers ('locators') to where useful material relating to that
heading can be found in a document.
(As def'ed by the English Wikipedia)
}
test
register.
That's the most remarkable thing I've read today. Maybe I need to be
more clear. A glossary is like a little dictionary in the back of a
book that defines the specialized words and phrases that the book uses
that might not be known to the general reader. Here is a definition
of glossary
understand something why don't you contact the
author, his email adress is right there on the first page.
more clear. A glossary is like a little dictionary in the back of a
book that defines the specialized words and phrases that the book uses
that might not be known to the general reader
I need to be
more clear. A glossary is like a little dictionary in the back of a
book that defines the specialized words and phrases that the book uses
that might not be known to the general reader. Here is a definition
of glossary:
A collection of glosses; a list with explanations
feature. I think
context knows how to make such buttons and to set bounding boxes
around words, so I think it should be possible, no?
___
If your question is of interest to others as well, please add an entry to the
Wiki
.
It's not done with javascript. As I understand it, the usual way is
to place an invisible pdf forms-style button over the word you want
to gloss and then set its short description feature. I think
context knows how to make such buttons and to set bounding boxes
around words, so I think
1301 - 1400 of 2270 matches
Mail list logo
