Non breaking small space

Non breaking small space

[Nigel King]

In LaTeX there is \, which is a small space which does not break easily at
the end of lines. It can be used as the space between say 10 and GHz.
Obviously I could use units but that seems to be a bit of a sledgehammer to
crack my nut. ConTeXt has |~| a small space but it breaks between lines. Is
there any solution that I have missed.
-- 
Nigel

Re: Non breaking small space

[John Culleton]

On Tuesday 30 April 2002 16:58, Nigel King wrote:
> In LaTeX there is \, which is a small space which does not break easily at
> the end of lines. It can be used as the space between say 10 and GHz.
> Obviously I could use units but that seems to be a bit of a sledgehammer to
> crack my nut. ConTeXt has |~| a small space but it breaks between lines. Is
> there any solution that I have missed.

Do you want it to break at eol or not?

You could try kerning, as in \kern .1667em (the definition of plain tex 
thinspace)

 Latex is based on TeX and the TeX primitives work.
You can even make it a macro as in:
\def\thinspace{\kern .1667 em} % (TeXBook p 352)

On the TeXBook p 96 it says that a kern is breakable if it is followed by 
glue. So to make it non-breakable try:

10\kern.1667em GHz.  

HTH 

John Culleton

Re: Non breaking small space

[Nigel King]

> From: John Culleton <john@wexfordpress.com>
> \def\thinspace{\kern .1667 em} % (TeXBook p 352)
Thanks John this is just what I wanted. I have actually defined in my
startup goodies

\def\,{\kern.1667em}

Which does not seem to corrupt anything else and is compatible with LaTeX
files from the past.
-- 
Nigel

Re: Non breaking small space

[Hans Hagen]

At 12:09 AM 5/4/2002 +0100, Nigel King wrote:
> > From: John Culleton <john@wexfordpress.com>
> > \def\thinspace{\kern .1667 em} % (TeXBook p 352)
>Thanks John this is just what I wanted. I have actually defined in my
>startup goodies
>
>\def\,{\kern.1667em}
>
>Which does not seem to corrupt anything else and is compatible with LaTeX
>files from the past.

maybe i should collect this kind of things in something m-latex.tex -)

   \def\,{\ifmmode\mskip\thinmuskip\else\thinspace\fi}

is better

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

"LaTeX compatibility module" (was: Non breaking small space)

[Henning Hraban Ramm]

Am Montag, 6. Mai 2002 02:09 schrieb Hans Hagen:
> maybe i should collect this kind of things in something m-latex.tex -)
>    \def\,{\ifmmode\mskip\thinmuskip\else\thinspace\fi}

I thought about making a "LaTeX environments" include file, so that my simple 
Perl scripts can translate at least the usual LaTeX \begin{something} .. 
\end{something} environments directly to \startsomething ... \stopsomething.

It would be only a collection of "\definestartstop"s that should give a 
similar look like the LaTeX environments.

Is there any interest in such?

Grüßlis vom Hraban!
-- 
http://www.fiee.net/texnique/
---

Re: "LaTeX compatibility module" (was: Non breaking small space)

[Idris Samawi Hamid]

>I thought about making a "LaTeX environments" include file, so that my simple 
>Perl scripts can translate at least the usual LaTeX \begin{something} .. 
>\end{something} environments directly to \startsomething ... \stopsomething.

>Is there any interest in such?

Much interest here; I'm sure plenty of us besides myself have lots of legacy LaTeX files that need converting.

My real pipedream is an NFSS==>typescript perl converter but I guess that's heresy in these parts:->

==========================
Dr. Idris Samawi Hamid
Depatment of Philosophy
Colorado State University
Fort Collins, CO 80526

Re: "LaTeX compatibility module" (was: Non breaking small space)

[Taco]

Informational: here is the \newcommand definition from m-bib.tex

%D \subonderwerp{\LATEX\ support}
%D
%D \macros{newcommand}

%D Just about all databases define something that uses
%D \type{\newcommand}. This fake version does not cover
%D everything \type{\newcommand} does, but it should be
%D enough for simple definitions like the ones found in
%D \BIBTEX\ files.
%D
%D It would be cleaner to move this command
%D to some sort of \type{supp-ltx} file somewhere in
%D the future.

\def\@star@or@long#1%
   {\doifnextcharelse*{\afterassignment#1\let\next=}{#1}}

\def\newcommand{\@star@or@long\new@command}

\def\new@command#1{\@testopt{\@newcommand#1}0}

\def\@newcommand#1[#2]%
   {\doifnextcharelse[{\@xargdef#1[#2]}{\@argdef#1[#2]}}

\long\def\@argdef#1[#2]#3{\@yargdef#1\@ne{#2}{#3}}

\long\def\@xargdef#1[#2][#3]#4%
    {\@EA\def\@EA#1\@EA{%
          \@EA \do@testopt \@EA#1%
          \csname\string#1\endcsname {#3}}%
     \@EA\@yargdef
          \csname\string#1\endcsname
          \tw@ {#2}{#4}}

\def\@testopt#1#2{\doifnextcharelse[{#1}{#1[#2]}}

\def\do@testopt#1{\expandafter\@testopt }

\long\def\@yargdef#1#2#3%
 {\!!counta#3\relax
  \advance \!!counta \@ne
  \let\@hash@\relax
  \edef\!!tempa{\ifx#2\tw@ [\@hash@1]\fi}%
  \!!countb #2%
  \loop\ifnum\!!countb <\!!counta
         \edef\!!tempa{\!!tempa\@hash@\the\!!countb}%
         \advance\!!countb \@ne
  \repeat
  \let\@hash@##%
  \long\@EA\def\@EA#1\!!tempa}

\long\def\@reargdef#1[#2]{\@yargdef#1\@ne{#2}}

Re: Non breaking small space

[Hans Hagen]

At 10:12 AM 5/2/2002 -0400, John Culleton wrote:

>10\kern.1667em GHz.

10 \Giga \Herz

[given that the units module is loaded]

-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

Re: Non breaking small space

[Eckhart Guthöhrlein]

Am Mon, 2002-05-06 um 02.11 schrieb Hans Hagen:
> 10 \Giga \Herz
> 

This would be great ...  if m-units supported configurable spacing!

Eckhart

Re: Non breaking small space

[John Culleton]

On Sunday 05 May 2002 08:11 pm, Hans Hagen wrote:
> At 10:12 AM 5/2/2002 -0400, John Culleton wrote:
> >10\kern.1667em GHz.
>
> 10 \Giga \Herz
>
> [given that the units module is loaded]
>
> -------------------------------------------------------------------------
>                                    Hans Hagen | PRAGMA ADE | pragma@wxs.nl
>                     

Is the units version offered by Hans breakable or non-breakable?

Are there any typographic advantages to one version over the other?

As has been pointed out my version with the \kern statement can be
reduced to a brief macro. And my version is unbreakable.

John Culleton

Able Indexers and Typesetters
http://wexfordpress.com

Re: Non breaking small space

[Patrick Gundlach]

Nigel King <king@dircon.co.uk> writes:

Hi Nigel,

> In LaTeX there is \, which is a small space which does not break easily at
> the end of lines. It can be used as the space between say 10 and GHz.
> Obviously I could use units but that seems to be a bit of a sledgehammer to
> crack my nut. ConTeXt has |~| a small space but it breaks between lines. Is
> there any solution that I have missed.

You can define your own discretionaries like the |~| one:

\definetextmodediscretionary ,
  {\kern .1667 em}

So now you can say 'My new calculator runs with 10|,|GHz'. 

See supp-lan.tex for more discretionaries. 

Patrick

-- 
I'll fade into the darkness

Gamma bugs

[Idris Samawi Hamid]

Dear ConTeXtnicians,

In Gamma (ConTeXt compiled with Omega: texexec --make --alone --tex=omega en) it appears that the Omega's otp execution interferes with a number of ConTeXt's 
macros which are not sufficiently insulated. Consider the two files con-test3.tex and type-xxx.tex (cmss is the base font):

%=========con-test3=================
\usetypescriptfile[type-xxx]
\usetypescript[arabtest]
\setupbodyfont[omarab,10pt]

\def\latinunicode{\ocp\BasicLatinTexUni=lat2uni
      \ocp\BasicLatinUniToFont=uni2lat
      \ocplist\BasicLatinOCP=
      \addbeforeocplist 1 \BasicLatinTexUni
      \addbeforeocplist 1 \BasicLatinUniToFont
      \nullocplist
      \pushocplist\BasicLatinOCP}

\def\texencoding{\clearocplists}

 %\latinunicode

\showframe[text]

\starttext%

\showbodyfont%

\showbodyfontenvironment[omarab]

This is a test {\bfc This is a test} {\tfc This is a test} {\tfx This is a
test}

\switchtobodyfont[12pt] This is a test {\tfc This is a test}

\switchtobodyfont[big] This is a test {\tfc This is a test}
\switchtobodyfont[small] This is a test {\tfc This is a test}

\switchtobodyfont[8pt] This is a test {\tfc This is a test}

\switchtobodyfont[10pt] This is a test {\tfc This is a test}

\switchtobodyfont[12pt] This is a test {\tfc This is a test}

\switchtobodyfont[global] This is a test {\tfc This is a test}

\stoptext
%=========type-xxx==================
\starttypescript [naskh] [omega] [name]

   \definefontsynonym [OmegaArabic]      [cmss10]   % [omarab]
   \definefontsynonym [OmegaArabic-Bold] [cmssbx10] % [omarabb]

   \definefontsynonym [Naskh]      [OmegaArabic]
   \definefontsynonym [NaskhBold]  [OmegaArabic-Bold]

\stoptypescript

\starttypescript [naskh] [omega] [size]

   \definebodyfont
     [20.7pt,17.3pt,14.4pt,12pt,11pt,10pt,9pt,8pt,7pt,6pt]
     [rm]
     [tf=Naskh sa 1,
      bf=NaskhBold sa 1]

\stoptypescript

\starttypescript [arabtest]

   \definebodyfontenvironment
     [omarab]
     [default]
     [interlinespace=2.8ex]

  \definetypeface [omarab] [rm] [naskh] [omega] [omega] %[rscale=1.6]

\stoptypescript
===========================
If you leave \latinunicode uncommented then con-test3 will compile like an ordinary ConTeXt job. Uncomment it and funny things happen:

1. Whenever the text size is whatever size \setupbodyfont defaults to, \tfa, \tfb, \tfc, and \tfd will do nothing at all. So in con-test3,

\switchtobodyfont[10pt] This is a test {\tfc This is a test}

will reproduce <This is a test> twice at 10pt. Interestingly, \tfx and \tfxx work fine. If you change the setup to \setupbodyfont[omarab,12pt] then the line 

\switchtobodyfont[12pt] This is a test {\tfc This is a test}

will reproduce <This is a test> twice at 12pt.

This is really weird. I am at a loss at where to start. Where are \tf<variable> defined so that I can look at the \def's and see if I can modify them somehow (though 
ConTeXt's macros are really scary)?

Hans mentioned that omega crashes on his system but I hope he or someone else here can test this and help me find an answer.

2. I mentioned the once before but I was rather unclear then and hope to be more clear and also more general this time:

\showlayout, \showbodyfont, and \showbodyfontenvironment[omarab] do funny things when the otp's are loaded. \showlayout actually causes omega to crash. 
\showgrid does not print the margin numbers (probably because they are isolated from the otp list). I think the solution is to 

a. make sure the macros are isolated from the otp's being executed (although the grid line numbers in \showgrid are an exception here);

b. give an option to these commands for which font to print the chart out in general. For example, \showbodyfontenvironment[omarab][cmr] would mean to print the 
fontenvironment table in cmr. \showbodyfont[omarab][cmr][\myocplist bt] would show sample characters transcribed by `b' and `t' from omarab but print the table and 
verbatim commands in cmr. \myocplist would have to grouped so it affects nothing but the sample characters.

I am rather afraid to mess around with the ConTeXt macros myself. They look rather frightening. Please don't make me do it:-)..

Your help is greatly appreciated!

Best wishes
Idris

==========================
Dr. Idris Samawi Hamid
Depatment of Philosophy
Colorado State University
Fort Collins, CO 80526

defining environments

[Idris Samawi Hamid]

Dear folks,

How do I define my own environmet "myenvironment" so that I can declare

\startmyenvironment

\stopmyenvironment

Best wishes
Idris

==========================
Dr. Idris Samawi Hamid
Depatment of Philosophy
Colorado State University
Fort Collins, CO 80526

Re: defining environments

[Henning Hraban Ramm]

Am Sonntag, 5. Mai 2002 03:46 schrieb Idris Samawi Hamid:
> How do I define my own environmet "myenvironment" so that I can declare
> \startmyenvironment
> \stopmyenvironment

e.g.

\definestartstop	[CodeMode]%
	[before={\startbackground\startlines}, 	
	after={\stoplines\stopbackground},
	style={\tt}]

-- 
Grüßlis vom Hraban!
---

Re: defining environments

[Patrick Gundlach]

Idris Samawi Hamid <ishamid@attbi.com> writes:

Good morning,

> How do I define my own environmet "myenvironment" so that I can declare

> \startmyenvironment
> 
> \stopmyenvironment

Well, it might be interesting, what you want to archive. There are a
lot of different 'environments' that can be used with start/stop. The
most simplest is probably:

\starttext
\definestartstop[idris]
\startidris
Hello!
\stopidris
\stoptext

-- 
I'll fade into the darkness

Re: Gamma bugs

[Hans Hagen]

At 06:20 PM 5/4/2002 -0600, Idris Samawi Hamid wrote:

>%=========con-test3=================
>\usetypescriptfile[type-xxx]
>\usetypescript[arabtest]
>\setupbodyfont[omarab,10pt]
>
>\def\latinunicode{\ocp\BasicLatinTexUni=lat2uni
>       \ocp\BasicLatinUniToFont=uni2lat
>       \ocplist\BasicLatinOCP=
>       \addbeforeocplist 1 \BasicLatinTexUni
>       \addbeforeocplist 1 \BasicLatinUniToFont
>       \nullocplist
>       \pushocplist\BasicLatinOCP}

this kind of defs are best done with the filter definition macros

>\def\texencoding{\clearocplists}

so, is \clearocplists a primitive ? [can you mail me a properly pdf'd or 
ps'd manual of omega; i can only generate an ugly unreadable bitmap version 
with missing charactrers]

>If you leave \latinunicode uncommented then con-test3 will compile like an 
>ordinary ConTeXt job. Uncomment it and funny things happen:

hm, maybe we need to hook some otp disabling code to the framework that 
reads system files
\
>Hans mentioned that omega crashes on his system but I hope he or someone 
>else here can test this and help me find an answer.

the latest fptex binaries work, so i can now generate an omega format (at 
the cost of large mem values)

>2. I mentioned the once before but I was rather unclear then and hope to 
>be more clear and also more general this time:
>
>\showlayout, \showbodyfont, and \showbodyfontenvironment[omarab] do funny 
>things when the otp's are loaded. \showlayout actually causes omega to crash.
>\showgrid does not print the margin numbers (probably because they are 
>isolated from the otp list). I think the solution is to

this maybe due to otp lookahead (omega is a hungry program); i got quite 
some \CLOBBERED (funny enough an undefined primitive) messages to the screen;

>fontenvironment table in cmr. \showbodyfont[omarab][cmr][\myocplist bt] 
>would show sample characters transcribed by `b' and `t' from omarab but 
>print the table and
>verbatim commands in cmr. \myocplist would have to grouped so it affects 
>nothing but the sample characters.

that's for later,

>I am rather afraid to mess around with the ConTeXt macros myself. They 
>look rather frightening. Please don't make me do it:-)..

not needed, there are enough hooks to get things done properly

btw, adding

   \definetypeface [omarab] [tt] [mono] [computer-modern] [default]

to the xxx file helps -)
Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

Re: Non breaking small space

[Hans Hagen]

At 09:58 PM 4/30/2002 +0100, Nigel King wrote:
>In LaTeX there is \, which is a small space which does not break easily at
>the end of lines. It can be used as the space between say 10 and GHz.
>Obviously I could use units but that seems to be a bit of a sledgehammer to
>crack my nut. ConTeXt has |~| a small space but it breaks between lines. Is
>there any solution that I have missed.

The next release will have the \, etc macros defined in a way similar to 
the math module (although configurable by means of the \definehspace feature).

Hans

-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------