In a message some time ago, Wolfgang suggested that
\def\ {\thinspace}
would serve to get non-expanding or non-stretchable spaces after
periods that occur within sentences and in bibliographies. When I
discovered that, while this worked well in limited contexts, in a
lengthy bibliography
re are two corrections I made. Perhaps they
will help.
1. line 286: changed \insertpublisher{. }{.}{.} to \insertpublisher
{ }{.}{.}
Why: prevents double periods after the title. It's what you did for
several other publication types in the version you sent me on August 10.
2. line 384: comm
Taco Hoekwater wrote
> Michael Green wrote:
>
>>
>> The first problem, with the two periods after a book title, has been
>> with me since at least last year. I can reproduce it with the
>> following:
>>
>> [A] ConTeXt version.
>>
>> C
Michael Green wrote:
The first problem, with the two periods after a book title, has been
with me since at least last year. I can reproduce it with the following:
[A] ConTeXt version.
ConTeXt ver: 2008.08.05 18:47 MKIV fmt: 2008.8.6 int: english/english
Ah. This is using an
Taco Hoekwater wrote:
Michael Green wrote:
[snip]
(1) I get two periods after a book title when using
\setuppublications[alternative=apa].
[snip]
This happens with all books. On looking at the source, I'm afraid I
can't track down where it's coming from or how to fix it.
(2)
; Title = {From Irenaeus to Grotius: a sourcebook in Christian
> political thought, 100-1625},
> Year = {1999}}
>
> (1) I get two periods after a book title when using
> \setuppublications[alternative=apa]. For this particular entry, here is
> what I get.
>
> O&#x
rcebook in Christian
political thought, 100-1625},
Year = {1999}}
(1) I get two periods after a book title when using \setuppublications
[alternative=apa]. For this particular entry, here is what I get.
O'Donovan, J. L. and O'Donovan, O. (1999). From Irenaeus to Grotius:
a sou
he title entry in the bib-file is a punctuation
>> character (say ! or ?), then we do not append a period?
>
> No, not at this time, sorry.
>
> Best wishes,
> Taco
>
Taco,
thanks for the response. Over the weekend I found a solution to my problem:
Instead of handling pun
inality or topology in the problem domain.
First of all, some do make a distinction between intraword and interword
spacing, although this need not necessarily be made. It does become
helpful, however, when setting Sperrdruck and noting the rules for
commas, periods, etc. The soul package in LaTeX does
mbered
>> itemization so that the stoppers (periods) are vertically aligned?
>> What I want should look like this:
>>
>> 1. an entry
>> 2. an entry
>> ...
>> 10. an entry
>>
>> Many thanks.
>
> \startitemize[n,fit,b
On Mon, Apr 21, 2008 at 3:35 PM, Alan Bowen <[EMAIL PROTECTED]> wrote:
> Can anyone point me to instructions/explanations of how to set up a numbered
> itemization so that the stoppers (periods) are vertically aligned?
> What I want should look like this:
>
> 1. an entry
>
Can anyone point me to instructions/explanations of how to set up a
numbered itemization so that the stoppers (periods) are vertically
aligned?
What I want should look like this:
1. an entry
2. an entry
...
10. an entry
Many thanks
b2c from
> > > > >
> /tmp/luatex-cache/context/6300afb4995fe38c77e9b86ed1ef1028/trees/f7d1b3c25487ab1e1035aff1c53b90da
> > > > > MtxRun | locating list of /home/nemo/.texmf-config
> > > > > MtxRun | locating list of /home/nemo/.texmf-var
> > > >
t; > >
> > > > MtxRun | loading configuration for /usr/share/texmf/web2c from
> > > >
> > /tmp/luatex-cache/context/6300afb4995fe38c77e9b86ed1ef1028/trees/f7d1b3c25487ab1e1035aff1c53b90da
> > > > MtxRun | locating list of /home/nemo/.texmf-c
/trees/f7d1b3c25487ab1e1035aff1c53b90da
> > > MtxRun | locating list of /home/nemo/.texmf-config
> > > MtxRun | locating list of /home/nemo/.texmf-var
> > > MtxRun | locating list of /home/nemo/texmf
> >
> > what strange paths: these periods
>
> Umm.
onfiguration for /usr/share/texmf/web2c from
> > /tmp/luatex-cache/context/6300afb4995fe38c77e9b86ed1ef1028/trees/f7d1b3c25487ab1e1035aff1c53b90da
> > MtxRun | locating list of /home/nemo/.texmf-config
> > MtxRun | locating list of /home/nemo/.texmf-var
> > MtxRun | locating list
1c53b90da
> MtxRun | locating list of /home/nemo/.texmf-config
> MtxRun | locating list of /home/nemo/.texmf-var
> MtxRun | locating list of /home/nemo/texmf
what strange paths: these periods
-
every couple of years or
>> so.
>> So try and see.
>
> It looks like this is more complicated than I thought. What would I do
> if I wanted old-style numerals just for a table of contents? Currently,
> my table of contents is set up like so:
>
> \setupcombinedlist[c
"Idris Samawi Hamid" <[EMAIL PROTECTED]> writes:
> On Fri, 22 Feb 2008 20:03:12 -0700, Jesse Alama <[EMAIL PROTECTED]> wrote:
>
>> I tried switching to nice old-style numerals for a table of contents,
>> and found to my chagrin that the periods in the n
Jesse Alama wrote:
> I tried switching to nice old-style numerals for a table of contents,
> and found to my chagrin that the periods in the numbers, such as the "."
> in "2.3", get typeset as triangles. You can see the result (verified on
> the live context in th
Hi,
On Fri, 22 Feb 2008 20:03:12 -0700, Jesse Alama <[EMAIL PROTECTED]> wrote:
> I tried switching to nice old-style numerals for a table of contents,
> and found to my chagrin that the periods in the numbers, such as the "."
> in "2.3", get typeset as
I tried switching to nice old-style numerals for a table of contents,
and found to my chagrin that the periods in the numbers, such as the "."
in "2.3", get typeset as triangles. You can see the result (verified on
the live context in the garden) with
\starttext
{\os 2.3}
text}
\nomarking{text}
\nomoreblocks
\nomorefiles
\nop
\nospace
\note[reference]
\notopandbottomlines
\nowhitespace
# \NR
\numbers{text}
\overbar{text}
\overbars{text text}
# \overlaybutton
# \overlayfigure
\overstrike{text}
\overstrikes{text text}
\packed
\page[options]
\pagereference[reference]
t; > ' -> right single quote (I'm, isn't etc.)
> >
> > Sure this is important, I suggest to add the horizontal ellipsis
>
> \dots? But what if one decides to use, say, 10 dots in a row? That
\periods[10]
> might lead to weird effects (non-evenly spaced do
measured by dramatically reduced demand charges and the
> opportunity to participate in DR programs, are substantial, often creating a
> project payback in the range of 1 to 18 months, - not to mention the
> benefits to local energy utilities struggling to keep power to their
> customers duri
charges and the
opportunity to participate in DR programs, are substantial, often creating a
project payback in the range of 1 to 18 months, - not to mention the
benefits to local energy utilities struggling to keep power to their
customers during peak usage periods."
As part of the fina
..-)
>
> (at least as an official synonym...)
Hi Idris,
text \textellipsis
>
> Note that you could also have \setupellipsis: '...' is the most prevalent
> but not the only form it can take. '***' and \emdash are apparent
> alternatives...
you can use \
gt; > \setuplabeltext[de][section=]
>> >
>> > Aditya
>>
>> Nice try, but no cigar :-) Even with
>>\setuplabeltext[deo][...], it
>> still gobbels the periods after the converted numbers.
>>Strange...
>> Thanks for your help, Aditya!
>
2007/3/19, Thomas A. Schmitz <[EMAIL PROTECTED]>:
On Mar 19, 2007, at 4:46 PM, Aditya Mahajan wrote:
> (Untested)
>
> \setuplabeltext[de][section=]
>
> Aditya
Nice try, but no cigar :-) Even with \setuplabeltext[deo][...], it
still gobbels the periods after the conve
On Mar 19, 2007, at 4:46 PM, Aditya Mahajan wrote:
> (Untested)
>
> \setuplabeltext[de][section=]
>
> Aditya
Nice try, but no cigar :-) Even with \setuplabeltext[deo][...], it
still gobbels the periods after the converted numbers. Strange...
Thanks for your help,
Taco Hoekwater wrote:
>
> >> Should \textellipsis be used for "2026 HORIZONTAL ELLIPSIS"
>
> Yes. But on the baseline, so:
OK, thanks.
>\definecharacter textellipsis {\periods\relax}
So perhaps fix the unic-032.tex again then.
> I believe there is a
textellipsis be used for "2026 HORIZONTAL ELLIPSIS"
Yes. But on the baseline, so:
\definecharacter textellipsis {\periods\relax}
U+2024 (ONE-DOT LEADER):
\definecharacter textonedotleader {\doperiods[1]}
U+2025 (TWO-DOT LEADER):
\definecharacter texttwodotleader {
;t think nobody is interested in your new beta: I
dlded it today and played with it, but had to revert to the old
version because it somehow did not honor the modifications I made
to \setuppublicationlayout (I was getting some default instead of
my own version, and there were spuriou
some default instead of my own
version, and there were spurious periods and colons in all the
entries).
I saw those in my (very small) example file as well, but that is
from a database that is known to have flaws so I didn't investigate
any further and just assumed that they were caused
, and there were spurious periods and colons in all the
entries). I will test it again within the next few days. By the way:
I spent one hour last weekend and, by judiciously sprinkling some
\unskip's in my definitions, had gotten rid of the extra spaces. I
actually wanted to write to yo
> The adaptations in the bst file are not many, unless you want to change
> the commas and periods as well.
No, the standards in typesetting are not that different from English.
Perhaps there's even an include-command...
> The only serious problem I encounter now is the language
Hello Adam,
Why not save the document as cont.au-de.bst and use it when you write
German. When you need the English version, you simply switch back to
cont.au.bst?
The adaptations in the bst file are not many, unless you want to change
the commas and periods as well.
The only serious problem I
the author, regardless of which portions are included. I
used ~ for spacing to ensure that a name is not split between its components
and to provide consistent spacing after the periods.
Stefano
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Nik
Am Montag, 05.01.04, um 05:52 Uhr (Europe/Zurich) schrieb Tyler Eaves:
One file to act with all the layout commands.
Use an "environment" file of the project structure.
One file for each class periods notes
Use an "component" file of the project structure.
(I'll writ
mething like this.
Pointers on how to acheive this would be most welcome.
One file to act with all the layout commands.
One file for each class periods notes
(I'll write a little ruby or python scribt to geneate the appropriate
\inputs in the main file)
In the main file:
Table of Content
101 - 140 of 140 matches
Mail list logo
