noun in index

[Jürgen Lange]

Hello all,
I tried to add a noun to the index. (mark word - toggle noun - Index  
entry)

Unfortunately the small-caps format of the noun is lost in Index.
Is this behavior intended?

regards
Jürgen

--

test3.lyx
Description: Binary data


test3.pdf
Description: Adobe PDF document

Re: noun in index

[Andrew Parsloe]

On 23/06/2013 7:36 p.m., Jürgen Lange wrote:

Hello all,
I tried to add a noun to the index. (mark word - toggle noun - Index
entry)
Unfortunately the small-caps format of the noun is lost in Index.
Is this behavior intended?

regards
Jürgen

--

If you look in the View Source window you'll see that you have got

\noun{Test\index{Test@\noun{Test}}}

whereas what you want is

\noun{Test}\index{Test@\noun{Test}}

(Turn the nouning off before clicking on the Insert index entry button, 
then format the text inside the index inset.)


Andrew

noun in index

[Jürgen Lange]

Hello all,
I tried to add a noun to the index. (mark word - toggle noun - Index  
entry)

Unfortunately the small-caps format of the noun is lost in Index.
Is this behavior intended?

regards
Jürgen

--

test3.lyx
Description: Binary data


test3.pdf
Description: Adobe PDF document

Re: noun in index

[Andrew Parsloe]

On 23/06/2013 7:36 p.m., Jürgen Lange wrote:

Hello all,
I tried to add a noun to the index. (mark word - toggle noun - Index
entry)
Unfortunately the small-caps format of the noun is lost in Index.
Is this behavior intended?

regards
Jürgen

--

If you look in the View Source window you'll see that you have got

\noun{Test\index{Test@\noun{Test}}}

whereas what you want is

\noun{Test}\index{Test@\noun{Test}}

(Turn the nouning off before clicking on the Insert index entry button, 
then format the text inside the index inset.)


Andrew

noun in index

[Jürgen Lange]

Hello all,
I tried to add a "noun" to the index. (mark word -> toggle noun -> Index  
entry)

Unfortunately the small-caps format of the noun is lost in Index.
Is this behavior intended?

regards
Jürgen

--

test3.lyx
Description: Binary data


test3.pdf
Description: Adobe PDF document

Re: noun in index

[Andrew Parsloe]

On 23/06/2013 7:36 p.m., Jürgen Lange wrote:

Hello all,
I tried to add a "noun" to the index. (mark word -> toggle noun -> Index
entry)
Unfortunately the small-caps format of the noun is lost in Index.
Is this behavior intended?

regards
Jürgen

--

If you look in the View Source window you'll see that you have got

\noun{Test\index{Test@\noun{Test}}}

whereas what you want is

\noun{Test}\index{Test@\noun{Test}}

(Turn the nouning off before clicking on the Insert index entry button, 
then format the text inside the index inset.)


Andrew

Re: Noun (smallcaps) in Section title

[Guenter Milde]

On 2011-06-28, Manolo Martínez wrote:
 Hello everyone,

 A quick question. If I use the Noun character style in a Section title, 
 article(paper) ignores me and renders it in lowercase. Is there a way to 
 override the style in this particular respect?

This depends on the font choice. Some font families are missing a bold
small caps variant. The LaTeX log will show you a font substition warning
in this case. I found this to be the case with e.g. Latin Modern.

Günter

Re: Noun (smallcaps) in Section title

[Paul Rubin]

Manolo Martínez manolo at austrohungaro.com writes:

 A quick question. If I use the Noun character style in a Section title, 
 article(paper) ignores me and renders it in lowercase. Is there a way to 
 override the style in this particular respect?

Document classes frequently dictate the font for headings (overruling your
choice). The sectsty package allows you to set font styles for headings, but it
does not work with article(paper).  If you're willing to switch to a class
sectsty supports, that is one way to get what you want.  Another possibility is
to put this in your preamble:

\usepackage{titlesec}
\titleformat*{\section}{\bfseries\sc}

That will put section titles in small caps, but they will not be bold face.

Paul

Re: Noun (smallcaps) in Section title

[Guenter Milde]

On 2011-06-28, Manolo Martínez wrote:
 Hello everyone,

 A quick question. If I use the Noun character style in a Section title, 
 article(paper) ignores me and renders it in lowercase. Is there a way to 
 override the style in this particular respect?

This depends on the font choice. Some font families are missing a bold
small caps variant. The LaTeX log will show you a font substition warning
in this case. I found this to be the case with e.g. Latin Modern.

Günter

Re: Noun (smallcaps) in Section title

[Paul Rubin]

Manolo Martínez manolo at austrohungaro.com writes:

 A quick question. If I use the Noun character style in a Section title, 
 article(paper) ignores me and renders it in lowercase. Is there a way to 
 override the style in this particular respect?

Document classes frequently dictate the font for headings (overruling your
choice). The sectsty package allows you to set font styles for headings, but it
does not work with article(paper).  If you're willing to switch to a class
sectsty supports, that is one way to get what you want.  Another possibility is
to put this in your preamble:

\usepackage{titlesec}
\titleformat*{\section}{\bfseries\sc}

That will put section titles in small caps, but they will not be bold face.

Paul

Re: Noun (smallcaps) in Section title

[Guenter Milde]

On 2011-06-28, Manolo Martínez wrote:
> Hello everyone,

> A quick question. If I use the Noun character style in a Section title, 
> article(paper) ignores me and renders it in lowercase. Is there a way to 
> override the style in this particular respect?

This depends on the font choice. Some font families are missing a bold
small caps variant. The LaTeX log will show you a font substition warning
in this case. I found this to be the case with e.g. Latin Modern.

Günter

Re: Noun (smallcaps) in Section title

[Paul Rubin]

Manolo Martínez  austrohungaro.com> writes:

> A quick question. If I use the Noun character style in a Section title, 
> article(paper) ignores me and renders it in lowercase. Is there a way to 
> override the style in this particular respect?

Document classes frequently dictate the font for headings (overruling your
choice). The sectsty package allows you to set font styles for headings, but it
does not work with article(paper).  If you're willing to switch to a class
sectsty supports, that is one way to get what you want.  Another possibility is
to put this in your preamble:

\usepackage{titlesec}
\titleformat*{\section}{\bfseries\sc}

That will put section titles in small caps, but they will not be bold face.

Paul

Noun (smallcaps) in Section title

[Manolo Martínez]

Hello everyone,

A quick question. If I use the Noun character style in a Section title, 
article(paper) ignores me and renders it in lowercase. Is there a way to 
override the style in this particular respect?


Thanks a lot,
Manolo

Noun (smallcaps) in Section title

[Manolo Martínez]

Hello everyone,

A quick question. If I use the Noun character style in a Section title, 
article(paper) ignores me and renders it in lowercase. Is there a way to 
override the style in this particular respect?


Thanks a lot,
Manolo

Noun (smallcaps) in Section title

[Manolo Martínez]

Hello everyone,

A quick question. If I use the Noun character style in a Section title, 
article(paper) ignores me and renders it in lowercase. Is there a way to 
override the style in this particular respect?


Thanks a lot,
Manolo

Re: puzzled by the \noun command inside \index

[stefano franchi]

On Sat, Dec 4, 2010 at 1:46 AM, Jürgen Spitzmüller sp...@lyx.org wrote:

 stefano franchi wrote:
  Latex 2: This is line of text with a word in small caps:
  \noun{small-caps-word}\index{small-caps-w...@\noun{small-caps-word}}
  ^^^
 
  whereas I would expect:
 
 
  Latex 3: This is line of text with a word in small caps:
  \noun{small-caps-word}\index{\noun{small-caps-word}}
 
 
 
  Why is the underlined part there? I mean the -- small-caps-word@ . Is
 it
  needed? Is it a bug? I have a feeling that it is messing up my index,
 even
  though I do not get any warning (let alone errors).

 It is needed to get your index entry sorted properly. If it would only be
 \index{\noun{small-caps-word}}, your entry would be sorted at \ (and then
 n). The part before the @ is a hint to the index processor where to
 sort
 the entry.



Thanks Jurgen, that makes sense. U nfortunately, it also means I have tio
look elsewhere to debug my index sorting issues...

Cheers,

Stefano

 HTH,
 Jürgen

Re: puzzled by the \noun command inside \index

[stefano franchi]

On Sat, Dec 4, 2010 at 1:46 AM, Jürgen Spitzmüller sp...@lyx.org wrote:

 stefano franchi wrote:
  Latex 2: This is line of text with a word in small caps:
  \noun{small-caps-word}\index{small-caps-w...@\noun{small-caps-word}}
  ^^^
 
  whereas I would expect:
 
 
  Latex 3: This is line of text with a word in small caps:
  \noun{small-caps-word}\index{\noun{small-caps-word}}
 
 
 
  Why is the underlined part there? I mean the -- small-caps-word@ . Is
 it
  needed? Is it a bug? I have a feeling that it is messing up my index,
 even
  though I do not get any warning (let alone errors).

 It is needed to get your index entry sorted properly. If it would only be
 \index{\noun{small-caps-word}}, your entry would be sorted at \ (and then
 n). The part before the @ is a hint to the index processor where to
 sort
 the entry.



Thanks Jurgen, that makes sense. U nfortunately, it also means I have tio
look elsewhere to debug my index sorting issues...

Cheers,

Stefano

 HTH,
 Jürgen

Re: puzzled by the \noun command inside \index

[stefano franchi]

On Sat, Dec 4, 2010 at 1:46 AM, Jürgen Spitzmüller <sp...@lyx.org> wrote:

> stefano franchi wrote:
> > Latex 2: This is line of text with a word in small caps:
> > \noun{small-caps-word}\index{small-caps-w...@\noun{small-caps-word}}
> > ^^^
> >
> > whereas I would expect:
> >
> >
> > Latex 3: This is line of text with a word in small caps:
> > \noun{small-caps-word}\index{\noun{small-caps-word}}
> >
> >
> >
> > Why is the underlined part there? I mean the --> small-caps-word@ . Is
> it
> > needed? Is it a bug? I have a feeling that it is messing up my index,
> even
> > though I do not get any warning (let alone errors).
>
> It is needed to get your index entry sorted properly. If it would only be
> \index{\noun{small-caps-word}}, your entry would be sorted at "\" (and then
> "n"). The part before the "@" is a hint to the index processor where to
> sort
> the entry.
>
>

Thanks Jurgen, that makes sense. U nfortunately, it also means I have tio
look elsewhere to debug my index sorting issues...

Cheers,

Stefano

> HTH,
> Jürgen
>

puzzled by the \noun command inside \index

[stefano franchi]

Dear Lyxers,

can anyone explain to me why the \noun command (small caps) produces this
funny latex code when used within a \idex command? Consider the following:

 This is a line of text with with a word in small caps: small-caps-word

shows up in the LateX source window as :

Latex 1: This is line of text with a word in small caps: \noun{word}


As it should.



Now try to put the last word of the previous line into a index command and
put it in small caps as well. This is the Latex output:


Latex 2: This is line of text with a word in small caps:
\noun{small-caps-word}\index{small-caps-w...@\noun{small-caps-word}}
^^^

whereas I would expect:


Latex 3: This is line of text with a word in small caps:
\noun{small-caps-word}\index{\noun{small-caps-word}}



Why is the underlined part there? I mean the -- small-caps-word@ . Is it
needed? Is it a bug? I have a feeling that it is messing up my index, even
though I do not get any warning (let alone errors).

Stefano


noun-command-test.lyx
Description: Binary data

Re: puzzled by the \noun command inside \index

[Jürgen Spitzmüller]

stefano franchi wrote:
 Latex 2: This is line of text with a word in small caps:
 \noun{small-caps-word}\index{small-caps-w...@\noun{small-caps-word}}
 ^^^
 
 whereas I would expect:
 
 
 Latex 3: This is line of text with a word in small caps:
 \noun{small-caps-word}\index{\noun{small-caps-word}}
 
 
 
 Why is the underlined part there? I mean the -- small-caps-word@ . Is it
 needed? Is it a bug? I have a feeling that it is messing up my index, even
 though I do not get any warning (let alone errors).

It is needed to get your index entry sorted properly. If it would only be 
\index{\noun{small-caps-word}}, your entry would be sorted at \ (and then 
n). The part before the @ is a hint to the index processor where to sort 
the entry.

HTH,
Jürgen

puzzled by the \noun command inside \index

[stefano franchi]

Dear Lyxers,

can anyone explain to me why the \noun command (small caps) produces this
funny latex code when used within a \idex command? Consider the following:

 This is a line of text with with a word in small caps: small-caps-word

shows up in the LateX source window as :

Latex 1: This is line of text with a word in small caps: \noun{word}


As it should.



Now try to put the last word of the previous line into a index command and
put it in small caps as well. This is the Latex output:


Latex 2: This is line of text with a word in small caps:
\noun{small-caps-word}\index{small-caps-w...@\noun{small-caps-word}}
^^^

whereas I would expect:


Latex 3: This is line of text with a word in small caps:
\noun{small-caps-word}\index{\noun{small-caps-word}}



Why is the underlined part there? I mean the -- small-caps-word@ . Is it
needed? Is it a bug? I have a feeling that it is messing up my index, even
though I do not get any warning (let alone errors).

Stefano


noun-command-test.lyx
Description: Binary data

Re: puzzled by the \noun command inside \index

[Jürgen Spitzmüller]

stefano franchi wrote:
 Latex 2: This is line of text with a word in small caps:
 \noun{small-caps-word}\index{small-caps-w...@\noun{small-caps-word}}
 ^^^
 
 whereas I would expect:
 
 
 Latex 3: This is line of text with a word in small caps:
 \noun{small-caps-word}\index{\noun{small-caps-word}}
 
 
 
 Why is the underlined part there? I mean the -- small-caps-word@ . Is it
 needed? Is it a bug? I have a feeling that it is messing up my index, even
 though I do not get any warning (let alone errors).

It is needed to get your index entry sorted properly. If it would only be 
\index{\noun{small-caps-word}}, your entry would be sorted at \ (and then 
n). The part before the @ is a hint to the index processor where to sort 
the entry.

HTH,
Jürgen

puzzled by the \noun command inside \index

[stefano franchi]

Dear Lyxers,

can anyone explain to me why the \noun command (small caps) produces this
funny latex code when used within a \idex command? Consider the following:

> This is a line of text with with a word in small caps: small-caps-word

shows up in the LateX source window as :

Latex 1: This is line of text with a word in small caps: \noun{word}


As it should.



Now try to put the last word of the previous line into a index command and
put it in small caps as well. This is the Latex output:


Latex 2: This is line of text with a word in small caps:
\noun{small-caps-word}\index{small-caps-w...@\noun{small-caps-word}}
^^^

whereas I would expect:


Latex 3: This is line of text with a word in small caps:
\noun{small-caps-word}\index{\noun{small-caps-word}}



Why is the underlined part there? I mean the --> small-caps-word@ . Is it
needed? Is it a bug? I have a feeling that it is messing up my index, even
though I do not get any warning (let alone errors).

Stefano


noun-command-test.lyx
Description: Binary data

Re: puzzled by the \noun command inside \index

[Jürgen Spitzmüller]

stefano franchi wrote:
> Latex 2: This is line of text with a word in small caps:
> \noun{small-caps-word}\index{small-caps-w...@\noun{small-caps-word}}
> ^^^
> 
> whereas I would expect:
> 
> 
> Latex 3: This is line of text with a word in small caps:
> \noun{small-caps-word}\index{\noun{small-caps-word}}
> 
> 
> 
> Why is the underlined part there? I mean the --> small-caps-word@ . Is it
> needed? Is it a bug? I have a feeling that it is messing up my index, even
> though I do not get any warning (let alone errors).

It is needed to get your index entry sorted properly. If it would only be 
\index{\noun{small-caps-word}}, your entry would be sorted at "\" (and then 
"n"). The part before the "@" is a hint to the index processor where to sort 
the entry.

HTH,
Jürgen

\bind C-k font-noun

[Ralf]

Okay,

tried to edit the cua.bind file and failed.

This I found 

#\bind C-k   font-noun

I got rid of the '#' and restarted Lyx,
hoping that a C-k would toggle a noun, but alas, it didn't ...

What magic is needed here to let a C-k toggle the noun ?

Cheers
-Ralf
p.s. Lyx1.6.3 on WinXP and c:\Program Files\LyX 1.6.3\Resources\bind\cua.bind

Re: \bind C-k font-noun

[Ralf]

Ralf ralf.sc...@... writes:
[snip]
 #\bind C-k   font-noun
 
 I got rid of the '#' and restarted Lyx,
 hoping that a C-k would toggle a noun, but alas, it didn't ...
 
 What magic is needed here to let a C-k toggle the noun ?

a simple spell worked: instead of 'k' I used 'j':

\bind C-j   font-noun

did the trick - I assume the \bind C-k clashes 
with something else, well ...

Cheers
-Ralf

Re: \bind C-k font-noun

[Rich Shepard]

On Thu, 11 Jun 2009, Ralf wrote:


did the trick - I assume the \bind C-k clashes with something else, well


Ralf,

  Look in the preferences-short cuts menu to see all the bindings. I've
found in the latest version that editing the bindings in the short cuts
widget works better than directly editing the bind file.

Rich

--
Richard B. Shepard, Ph.D.   |  IntegrityCredibility
Applied Ecosystem Services, Inc.|Innovation
http://www.appl-ecosys.com Voice: 503-667-4517  Fax: 503-667-8863

Re: \bind C-k font-noun

[Ralf]

Rich Shepard rshep...@... writes:
[snip]
Look in the preferences-short cuts menu to see all the bindings. I've
 found in the latest version that editing the bindings in the short cuts
 widget works better than directly editing the bind file.

cheers mate! will do next time
-ralf

\bind C-k font-noun

[Ralf]

Okay,

tried to edit the cua.bind file and failed.

This I found 

#\bind C-k   font-noun

I got rid of the '#' and restarted Lyx,
hoping that a C-k would toggle a noun, but alas, it didn't ...

What magic is needed here to let a C-k toggle the noun ?

Cheers
-Ralf
p.s. Lyx1.6.3 on WinXP and c:\Program Files\LyX 1.6.3\Resources\bind\cua.bind

Re: \bind C-k font-noun

[Ralf]

Ralf ralf.sc...@... writes:
[snip]
 #\bind C-k   font-noun
 
 I got rid of the '#' and restarted Lyx,
 hoping that a C-k would toggle a noun, but alas, it didn't ...
 
 What magic is needed here to let a C-k toggle the noun ?

a simple spell worked: instead of 'k' I used 'j':

\bind C-j   font-noun

did the trick - I assume the \bind C-k clashes 
with something else, well ...

Cheers
-Ralf

Re: \bind C-k font-noun

[Rich Shepard]

On Thu, 11 Jun 2009, Ralf wrote:


did the trick - I assume the \bind C-k clashes with something else, well


Ralf,

  Look in the preferences-short cuts menu to see all the bindings. I've
found in the latest version that editing the bindings in the short cuts
widget works better than directly editing the bind file.

Rich

--
Richard B. Shepard, Ph.D.   |  IntegrityCredibility
Applied Ecosystem Services, Inc.|Innovation
http://www.appl-ecosys.com Voice: 503-667-4517  Fax: 503-667-8863

Re: \bind C-k font-noun

[Ralf]

Rich Shepard rshep...@... writes:
[snip]
Look in the preferences-short cuts menu to see all the bindings. I've
 found in the latest version that editing the bindings in the short cuts
 widget works better than directly editing the bind file.

cheers mate! will do next time
-ralf

\bind "C-k" "font-noun"

[Ralf]

Okay,

tried to edit the cua.bind file and failed.

This I found 

#\bind "C-k"   "font-noun"

I got rid of the '#' and restarted Lyx,
hoping that a C-k would toggle a noun, but alas, it didn't ...

What magic is needed here to let a C-k toggle the noun ?

Cheers
-Ralf
p.s. Lyx1.6.3 on WinXP and c:\Program Files\LyX 1.6.3\Resources\bind\cua.bind

Re: \bind "C-k" "font-noun"

[Ralf]

Ralf <ralf.sc...@...> writes:
[snip]
> #\bind "C-k"   "font-noun"
> 
> I got rid of the '#' and restarted Lyx,
> hoping that a C-k would toggle a noun, but alas, it didn't ...
> 
> What magic is needed here to let a C-k toggle the noun ?

a simple spell worked: instead of 'k' I used 'j':

\bind "C-j"   "font-noun"

did the trick - I assume the \bind "C-k" clashes 
with something else, well ...

Cheers
-Ralf

Re: \bind "C-k" "font-noun"

[Rich Shepard]

On Thu, 11 Jun 2009, Ralf wrote:


did the trick - I assume the \bind "C-k" clashes with something else, well


Ralf,

  Look in the preferences->short cuts menu to see all the bindings. I've
found in the latest version that editing the bindings in the short cuts
widget works better than directly editing the bind file.

Rich

--
Richard B. Shepard, Ph.D.   |  IntegrityCredibility
Applied Ecosystem Services, Inc.|Innovation
 Voice: 503-667-4517  Fax: 503-667-8863

Re: \bind "C-k" "font-noun"

[Ralf]

Rich Shepard  writes:
[snip]
>Look in the preferences->short cuts menu to see all the bindings. I've
> found in the latest version that editing the bindings in the short cuts
> widget works better than directly editing the bind file.

cheers mate! will do next time
-ralf

\noun in Tex environment

[phrygian]

Hi 

if tried to emphasize a word in the tex-environment with \noun but I receive
an Undefined Control Sequence Error.
Ex.: ERT(\begin{theorem} \noun{XchangeKey} \end{theorem}

I have included the following in the Latex preamble:
\usepackage{amsmath, amsfonts}

Can anyone tell what I can do to fix that?

Thanks!

phyrgian

-- 
View this message in context: 
http://n2.nabble.com/%5Cnoun-in-Tex-environment-tp1393414p1393414.html
Sent from the LyX - Users mailing list archive at Nabble.com.

Re: \noun in Tex environment

[phrygian]

Problem solved: I use the command \textsc{}


-- 
View this message in context: 
http://n2.nabble.com/%5Cnoun-in-Tex-environment-tp1393414p1393433.html
Sent from the LyX - Users mailing list archive at Nabble.com.

\noun in Tex environment

[phrygian]

Hi 

if tried to emphasize a word in the tex-environment with \noun but I receive
an Undefined Control Sequence Error.
Ex.: ERT(\begin{theorem} \noun{XchangeKey} \end{theorem}

I have included the following in the Latex preamble:
\usepackage{amsmath, amsfonts}

Can anyone tell what I can do to fix that?

Thanks!

phyrgian

-- 
View this message in context: 
http://n2.nabble.com/%5Cnoun-in-Tex-environment-tp1393414p1393414.html
Sent from the LyX - Users mailing list archive at Nabble.com.

Re: \noun in Tex environment

[phrygian]

Problem solved: I use the command \textsc{}


-- 
View this message in context: 
http://n2.nabble.com/%5Cnoun-in-Tex-environment-tp1393414p1393433.html
Sent from the LyX - Users mailing list archive at Nabble.com.

\noun in Tex environment

[phrygian]

Hi 

if tried to emphasize a word in the tex-environment with \noun but I receive
an Undefined Control Sequence Error.
Ex.: ERT(\begin{theorem} \noun{XchangeKey} \end{theorem}

I have included the following in the Latex preamble:
\usepackage{amsmath, amsfonts}

Can anyone tell what I can do to fix that?

Thanks!

phyrgian

-- 
View this message in context: 
http://n2.nabble.com/%5Cnoun-in-Tex-environment-tp1393414p1393414.html
Sent from the LyX - Users mailing list archive at Nabble.com.

Re: \noun in Tex environment

[phrygian]

Problem solved: I use the command \textsc{}


-- 
View this message in context: 
http://n2.nabble.com/%5Cnoun-in-Tex-environment-tp1393414p1393433.html
Sent from the LyX - Users mailing list archive at Nabble.com.

Re: search and replace noun style

[Abdelrazak Younes]

William Seager wrote:

Hi all. Does anyone know if there is a way to search
a document for a certain word and replace it with
the same word but in noun style (small caps)?


Open the lyx file in a text editor and search and replace the word xxx 
with the following (on three new lines):


\noun on
xxx
\noun default

Abdel.

Re: search and replace noun style

[Abdelrazak Younes]

William Seager wrote:

Hi all. Does anyone know if there is a way to search
a document for a certain word and replace it with
the same word but in noun style (small caps)?


Open the lyx file in a text editor and search and replace the word xxx 
with the following (on three new lines):


\noun on
xxx
\noun default

Abdel.

Re: search and replace noun style

[Abdelrazak Younes]

William Seager wrote:

Hi all. Does anyone know if there is a way to search
a document for a certain word and replace it with
the same word but in noun style (small caps)?


Open the lyx file in a text editor and search and replace the word xxx 
with the following (on three new lines):


\noun on
xxx
\noun default

Abdel.

search and replace noun style

[William Seager]

Hi all. Does anyone know if there is a way to search
a document for a certain word and replace it with
the same word but in noun style (small caps)?

thanks
-- 
William Seager
University of Toronto Scarborough
www.utsc.utoronto.ca/~seager

search and replace noun style

[William Seager]

Hi all. Does anyone know if there is a way to search
a document for a certain word and replace it with
the same word but in noun style (small caps)?

thanks
-- 
William Seager
University of Toronto Scarborough
www.utsc.utoronto.ca/~seager

search and replace noun style

[William Seager]

Hi all. Does anyone know if there is a way to search
a document for a certain word and replace it with
the same word but in noun style (small caps)?

thanks
-- 
William Seager
University of Toronto Scarborough
www.utsc.utoronto.ca/~seager

\noun

[Bruce Pourciau]

A paper of mine I used the Noun command in LyX to put various things  
in small caps. The exported tex file translates this into \noun. But  
the pdf that the journal built from this tex file, after it was  
uploaded on the journal's e-submission site, has no small caps. No  
does it have any italic text, which is marked by \emph in the  
exported tex file.


Do I have to force the small caps and italic with more specific  
commands?


Maybe I'll just send them a pdf built by _me_, and tell them to look  
at it. After all, they don't actually use latex to set the text of  
their journal.


Bruce

\noun

[Bruce Pourciau]

My latex books don't even list the command \noun in their indexes.

Bruce

Re: \noun

[Rich Shepard]

On Thu, 27 Jul 2006, Bruce Pourciau wrote:


My latex books don't even list the command \noun in their indexes.


Bruce,

  The LaTeX command is \sc (small caps); not every typeface has this font
defined. What is the text font in your document?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental Permitting
Applied Ecosystem Services, Inc.(TM)|Accelerator
http://www.appl-ecosys.com Voice: 503-667-4517  Fax: 503-667-8863

Re: \noun

[Bruce Pourciau]

  The LaTeX command is \sc (small caps); not every typeface has  
this font

defined. What is the text font in your document?


In the preamble, I have \usepackage[osf]{mathpazo}, so \noun produces  
real Palatino small caps locally (for me), but not for them. On the  
other hand, a previous tex file I uploaded had \usepackage{mathpazo}  
in the preamble (no osf), and the pdf they built from that file at  
least had the italic text in the correct places. I would think, even  
if their typeface has no true small caps, that \noun would produce  
fake small caps. And certainly \emph should produce italic, in  
general. Do I really have to go through the tex file and replace\emph  
with \it and \noun with \sc?


Bruce


On Jul 27, 2006, at 8:47 AM, Rich Shepard wrote:


On Thu, 27 Jul 2006, Bruce Pourciau wrote:


My latex books don't even list the command \noun in their indexes.


Bruce,

  The LaTeX command is \sc (small caps); not every typeface has  
this font

defined. What is the text font in your document?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental  
Permitting

Applied Ecosystem Services, Inc.(TM)|Accelerator
http://www.appl-ecosys.com Voice: 503-667-4517  Fax:  
503-667-8863

Re: \noun

[Bruce Pourciau]

The exported tex file converts \noun using \newcommand{\noun}[1] 
{\textsc{#1}}, before it lists \usepackage[osf]{mathpazo}.


Bruce



On Jul 27, 2006, at 8:47 AM, Rich Shepard wrote:


On Thu, 27 Jul 2006, Bruce Pourciau wrote:


My latex books don't even list the command \noun in their indexes.


Bruce,

  The LaTeX command is \sc (small caps); not every typeface has  
this font

defined. What is the text font in your document?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental  
Permitting

Applied Ecosystem Services, Inc.(TM)|Accelerator
http://www.appl-ecosys.com Voice: 503-667-4517  Fax:  
503-667-8863

Re: \noun

[Rich Shepard]

On Thu, 27 Jul 2006, Bruce Pourciau wrote:


Do I really have to go through the tex file and replace\emph with \it and
\noun with \sc?


Bruce,

  I would hope not! From what you wrote in your original message, it seems
the problem is on their end, since they don't have LaTeX installed. How are
they typesetting your article? Will they accept a camera-ready .pdf from you
if it's generated at a sufficiently high resolution?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental Permitting
Applied Ecosystem Services, Inc.(TM)|Accelerator
http://www.appl-ecosys.com Voice: 503-667-4517  Fax: 503-667-8863

Re: \noun

[Bruce Pourciau]

How are
they typesetting your article? Will they accept a camera-ready .pdf  
from you

if it's generated at a sufficiently high resolution?


I'll try to find out from the journal what they recommend to fix this  
problem. Thanks, Rich.


Bruce

On Jul 27, 2006, at 9:17 AM, Rich Shepard wrote:


On Thu, 27 Jul 2006, Bruce Pourciau wrote:

Do I really have to go through the tex file and replace\emph with  
\it and

\noun with \sc?


Bruce,

  I would hope not! From what you wrote in your original message,  
it seems
the problem is on their end, since they don't have LaTeX installed.  
How are
they typesetting your article? Will they accept a camera-ready .pdf  
from you

if it's generated at a sufficiently high resolution?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental  
Permitting

Applied Ecosystem Services, Inc.(TM)|Accelerator
http://www.appl-ecosys.com Voice: 503-667-4517  Fax:  
503-667-8863

Re: \noun

[Paul A. Rubin]

Bruce Pourciau wrote:


I'll try to find out from the journal what they recommend to fix this 
problem. Thanks, Rich.





You might ask the journal whether they apply their own style files or 
macros and, if so, whether they happen to have a macro named \noun 
(which might be redefining the one LyX puts in the exported LaTeX).


/Paul

Re: \noun

[Juergen Spitzmueller]

Bruce Pourciau wrote:
 Do I really have to go through the tex file and replace\emph  
 with \it and \noun with \sc?

No. \noun is semantic markup that uses a macro defined by LyX:

\newcommand{\noun}[1]{\textsc{#1}}

You see, it's really \textsc, but the advantage of semantic markup is that you 
can easily redefine \noun if needed (for instance, if you want the persons' 
names in full caps instead of small caps).

Does your publisher really hinder you from putting the above macro in the 
preamble?

You can also use \textsc in LyX, that's in Edit-Text Style-Shape-Small Caps 
(which is different from Edit-Text Style-Misc-Noun).

As to \emph, this is semantic markup, defined in LaTeX2e. Its advantage 
compared to \textit is that it has italic correction.

Oh, and btw, *never* use \sc and \it instead of \textsc and \textit.

Jürgen

Re: \noun

[Bruce Pourciau]

Thanks Jürgen and Paul. I'm now in conversation with the journal.

They accept latex files and can build from them on their e-submission  
site a pdf that the author can view for approval, but this pdf is  
only for viewing -- it has all the figures lined up at the beginning,  
for example. And in my case, for some reason, it also did not show  
italic or small caps in the correct places. The journal is not  
typeset with latex, so they must have a way to go from a latex file  
to something in their format that's at least roughly accurate. In any  
case, they have to check the latex file to see where the figures go,  
so it seems to me they can also check it to see where \emph and \noun  
= \textsc are marking italic and small caps.


Bruce




On Jul 27, 2006, at 11:23 AM, Juergen Spitzmueller wrote:


Bruce Pourciau wrote:

Do I really have to go through the tex file and replace\emph
with \it and \noun with \sc?


No. \noun is semantic markup that uses a macro defined by LyX:

\newcommand{\noun}[1]{\textsc{#1}}

You see, it's really \textsc, but the advantage of semantic markup  
is that you
can easily redefine \noun if needed (for instance, if you want the  
persons'

names in full caps instead of small caps).

Does your publisher really hinder you from putting the above macro  
in the

preamble?

You can also use \textsc in LyX, that's in Edit-Text Style-Shape- 
Small Caps

(which is different from Edit-Text Style-Misc-Noun).

As to \emph, this is semantic markup, defined in LaTeX2e. Its  
advantage

compared to \textit is that it has italic correction.

Oh, and btw, *never* use \sc and \it instead of \textsc and \textit.

Jürgen


Bruce Pourciau wrote:

I'll try to find out from the journal what they recommend to fix  
this problem. Thanks, Rich.





You might ask the journal whether they apply their own style files  
or macros and, if so, whether they happen to have a macro named  
\noun (which might be redefining the one LyX puts in the exported  
LaTeX).


/Paul

\noun

[Bruce Pourciau]

A paper of mine I used the Noun command in LyX to put various things  
in small caps. The exported tex file translates this into \noun. But  
the pdf that the journal built from this tex file, after it was  
uploaded on the journal's e-submission site, has no small caps. No  
does it have any italic text, which is marked by \emph in the  
exported tex file.


Do I have to force the small caps and italic with more specific  
commands?


Maybe I'll just send them a pdf built by _me_, and tell them to look  
at it. After all, they don't actually use latex to set the text of  
their journal.


Bruce

\noun

[Bruce Pourciau]

My latex books don't even list the command \noun in their indexes.

Bruce

Re: \noun

[Rich Shepard]

On Thu, 27 Jul 2006, Bruce Pourciau wrote:


My latex books don't even list the command \noun in their indexes.


Bruce,

  The LaTeX command is \sc (small caps); not every typeface has this font
defined. What is the text font in your document?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental Permitting
Applied Ecosystem Services, Inc.(TM)|Accelerator
http://www.appl-ecosys.com Voice: 503-667-4517  Fax: 503-667-8863

Re: \noun

[Bruce Pourciau]

  The LaTeX command is \sc (small caps); not every typeface has  
this font

defined. What is the text font in your document?


In the preamble, I have \usepackage[osf]{mathpazo}, so \noun produces  
real Palatino small caps locally (for me), but not for them. On the  
other hand, a previous tex file I uploaded had \usepackage{mathpazo}  
in the preamble (no osf), and the pdf they built from that file at  
least had the italic text in the correct places. I would think, even  
if their typeface has no true small caps, that \noun would produce  
fake small caps. And certainly \emph should produce italic, in  
general. Do I really have to go through the tex file and replace\emph  
with \it and \noun with \sc?


Bruce


On Jul 27, 2006, at 8:47 AM, Rich Shepard wrote:


On Thu, 27 Jul 2006, Bruce Pourciau wrote:


My latex books don't even list the command \noun in their indexes.


Bruce,

  The LaTeX command is \sc (small caps); not every typeface has  
this font

defined. What is the text font in your document?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental  
Permitting

Applied Ecosystem Services, Inc.(TM)|Accelerator
http://www.appl-ecosys.com Voice: 503-667-4517  Fax:  
503-667-8863

Re: \noun

[Bruce Pourciau]

The exported tex file converts \noun using \newcommand{\noun}[1] 
{\textsc{#1}}, before it lists \usepackage[osf]{mathpazo}.


Bruce



On Jul 27, 2006, at 8:47 AM, Rich Shepard wrote:


On Thu, 27 Jul 2006, Bruce Pourciau wrote:


My latex books don't even list the command \noun in their indexes.


Bruce,

  The LaTeX command is \sc (small caps); not every typeface has  
this font

defined. What is the text font in your document?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental  
Permitting

Applied Ecosystem Services, Inc.(TM)|Accelerator
http://www.appl-ecosys.com Voice: 503-667-4517  Fax:  
503-667-8863

Re: \noun

[Rich Shepard]

On Thu, 27 Jul 2006, Bruce Pourciau wrote:


Do I really have to go through the tex file and replace\emph with \it and
\noun with \sc?


Bruce,

  I would hope not! From what you wrote in your original message, it seems
the problem is on their end, since they don't have LaTeX installed. How are
they typesetting your article? Will they accept a camera-ready .pdf from you
if it's generated at a sufficiently high resolution?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental Permitting
Applied Ecosystem Services, Inc.(TM)|Accelerator
http://www.appl-ecosys.com Voice: 503-667-4517  Fax: 503-667-8863

Re: \noun

[Bruce Pourciau]

How are
they typesetting your article? Will they accept a camera-ready .pdf  
from you

if it's generated at a sufficiently high resolution?


I'll try to find out from the journal what they recommend to fix this  
problem. Thanks, Rich.


Bruce

On Jul 27, 2006, at 9:17 AM, Rich Shepard wrote:


On Thu, 27 Jul 2006, Bruce Pourciau wrote:

Do I really have to go through the tex file and replace\emph with  
\it and

\noun with \sc?


Bruce,

  I would hope not! From what you wrote in your original message,  
it seems
the problem is on their end, since they don't have LaTeX installed.  
How are
they typesetting your article? Will they accept a camera-ready .pdf  
from you

if it's generated at a sufficiently high resolution?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental  
Permitting

Applied Ecosystem Services, Inc.(TM)|Accelerator
http://www.appl-ecosys.com Voice: 503-667-4517  Fax:  
503-667-8863

Re: \noun

[Paul A. Rubin]

Bruce Pourciau wrote:


I'll try to find out from the journal what they recommend to fix this 
problem. Thanks, Rich.





You might ask the journal whether they apply their own style files or 
macros and, if so, whether they happen to have a macro named \noun 
(which might be redefining the one LyX puts in the exported LaTeX).


/Paul

Re: \noun

[Juergen Spitzmueller]

Bruce Pourciau wrote:
 Do I really have to go through the tex file and replace\emph  
 with \it and \noun with \sc?

No. \noun is semantic markup that uses a macro defined by LyX:

\newcommand{\noun}[1]{\textsc{#1}}

You see, it's really \textsc, but the advantage of semantic markup is that you 
can easily redefine \noun if needed (for instance, if you want the persons' 
names in full caps instead of small caps).

Does your publisher really hinder you from putting the above macro in the 
preamble?

You can also use \textsc in LyX, that's in Edit-Text Style-Shape-Small Caps 
(which is different from Edit-Text Style-Misc-Noun).

As to \emph, this is semantic markup, defined in LaTeX2e. Its advantage 
compared to \textit is that it has italic correction.

Oh, and btw, *never* use \sc and \it instead of \textsc and \textit.

Jürgen

Re: \noun

[Bruce Pourciau]

Thanks Jürgen and Paul. I'm now in conversation with the journal.

They accept latex files and can build from them on their e-submission  
site a pdf that the author can view for approval, but this pdf is  
only for viewing -- it has all the figures lined up at the beginning,  
for example. And in my case, for some reason, it also did not show  
italic or small caps in the correct places. The journal is not  
typeset with latex, so they must have a way to go from a latex file  
to something in their format that's at least roughly accurate. In any  
case, they have to check the latex file to see where the figures go,  
so it seems to me they can also check it to see where \emph and \noun  
= \textsc are marking italic and small caps.


Bruce




On Jul 27, 2006, at 11:23 AM, Juergen Spitzmueller wrote:


Bruce Pourciau wrote:

Do I really have to go through the tex file and replace\emph
with \it and \noun with \sc?


No. \noun is semantic markup that uses a macro defined by LyX:

\newcommand{\noun}[1]{\textsc{#1}}

You see, it's really \textsc, but the advantage of semantic markup  
is that you
can easily redefine \noun if needed (for instance, if you want the  
persons'

names in full caps instead of small caps).

Does your publisher really hinder you from putting the above macro  
in the

preamble?

You can also use \textsc in LyX, that's in Edit-Text Style-Shape- 
Small Caps

(which is different from Edit-Text Style-Misc-Noun).

As to \emph, this is semantic markup, defined in LaTeX2e. Its  
advantage

compared to \textit is that it has italic correction.

Oh, and btw, *never* use \sc and \it instead of \textsc and \textit.

Jürgen


Bruce Pourciau wrote:

I'll try to find out from the journal what they recommend to fix  
this problem. Thanks, Rich.





You might ask the journal whether they apply their own style files  
or macros and, if so, whether they happen to have a macro named  
\noun (which might be redefining the one LyX puts in the exported  
LaTeX).


/Paul

\noun

[Bruce Pourciau]

A paper of mine I used the Noun command in LyX to put various things  
in small caps. The exported tex file translates this into \noun. But  
the pdf that the journal built from this tex file, after it was  
uploaded on the journal's e-submission site, has no small caps. No  
does it have any italic text, which is marked by \emph in the  
exported tex file.


Do I have to force the small caps and italic with more specific  
commands?


Maybe I'll just send them a pdf built by _me_, and tell them to look  
at it. After all, they don't actually use latex to set the text of  
their journal.


Bruce

\noun

[Bruce Pourciau]

My latex books don't even list the command \noun in their indexes.

Bruce

Re: \noun

[Rich Shepard]

On Thu, 27 Jul 2006, Bruce Pourciau wrote:


My latex books don't even list the command \noun in their indexes.


Bruce,

  The LaTeX command is \sc (small caps); not every typeface has this font
defined. What is the text font in your document?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental Permitting
Applied Ecosystem Services, Inc.(TM)|Accelerator
<http://www.appl-ecosys.com> Voice: 503-667-4517  Fax: 503-667-8863

Re: \noun

[Bruce Pourciau]

  The LaTeX command is \sc (small caps); not every typeface has  
this font

defined. What is the text font in your document?


In the preamble, I have \usepackage[osf]{mathpazo}, so \noun produces  
real Palatino small caps locally (for me), but not for them. On the  
other hand, a previous tex file I uploaded had \usepackage{mathpazo}  
in the preamble (no osf), and the pdf they built from that file at  
least had the italic text in the correct places. I would think, even  
if their typeface has no true small caps, that \noun would produce  
fake small caps. And certainly \emph should produce italic, in  
general. Do I really have to go through the tex file and replace\emph  
with \it and \noun with \sc?


Bruce


On Jul 27, 2006, at 8:47 AM, Rich Shepard wrote:


On Thu, 27 Jul 2006, Bruce Pourciau wrote:


My latex books don't even list the command \noun in their indexes.


Bruce,

  The LaTeX command is \sc (small caps); not every typeface has  
this font

defined. What is the text font in your document?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental  
Permitting

Applied Ecosystem Services, Inc.(TM)|Accelerator
<http://www.appl-ecosys.com> Voice: 503-667-4517  Fax:  
503-667-8863

Re: \noun

[Bruce Pourciau]

The exported tex file converts \noun using \newcommand{\noun}[1] 
{\textsc{#1}}, before it lists \usepackage[osf]{mathpazo}.


Bruce



On Jul 27, 2006, at 8:47 AM, Rich Shepard wrote:


On Thu, 27 Jul 2006, Bruce Pourciau wrote:


My latex books don't even list the command \noun in their indexes.


Bruce,

  The LaTeX command is \sc (small caps); not every typeface has  
this font

defined. What is the text font in your document?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental  
Permitting

Applied Ecosystem Services, Inc.(TM)|Accelerator
<http://www.appl-ecosys.com> Voice: 503-667-4517  Fax:  
503-667-8863

Re: \noun

[Rich Shepard]

On Thu, 27 Jul 2006, Bruce Pourciau wrote:


Do I really have to go through the tex file and replace\emph with \it and
\noun with \sc?


Bruce,

  I would hope not! From what you wrote in your original message, it seems
the problem is on their end, since they don't have LaTeX installed. How are
they typesetting your article? Will they accept a camera-ready .pdf from you
if it's generated at a sufficiently high resolution?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental Permitting
Applied Ecosystem Services, Inc.(TM)|Accelerator
<http://www.appl-ecosys.com> Voice: 503-667-4517  Fax: 503-667-8863

Re: \noun

[Bruce Pourciau]

How are
they typesetting your article? Will they accept a camera-ready .pdf  
from you

if it's generated at a sufficiently high resolution?


I'll try to find out from the journal what they recommend to fix this  
problem. Thanks, Rich.


Bruce

On Jul 27, 2006, at 9:17 AM, Rich Shepard wrote:


On Thu, 27 Jul 2006, Bruce Pourciau wrote:

Do I really have to go through the tex file and replace\emph with  
\it and

\noun with \sc?


Bruce,

  I would hope not! From what you wrote in your original message,  
it seems
the problem is on their end, since they don't have LaTeX installed.  
How are
they typesetting your article? Will they accept a camera-ready .pdf  
from you

if it's generated at a sufficiently high resolution?

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental  
Permitting

Applied Ecosystem Services, Inc.(TM)|Accelerator
<http://www.appl-ecosys.com> Voice: 503-667-4517  Fax:  
503-667-8863

Re: \noun

[Paul A. Rubin]

Bruce Pourciau wrote:


I'll try to find out from the journal what they recommend to fix this 
problem. Thanks, Rich.





You might ask the journal whether they apply their own style files or 
macros and, if so, whether they happen to have a macro named \noun 
(which might be redefining the one LyX puts in the exported LaTeX).


/Paul

Re: \noun

[Juergen Spitzmueller]

Bruce Pourciau wrote:
> Do I really have to go through the tex file and replace\emph  
> with \it and \noun with \sc?

No. \noun is semantic markup that uses a macro defined by LyX:

\newcommand{\noun}[1]{\textsc{#1}}

You see, it's really \textsc, but the advantage of semantic markup is that you 
can easily redefine \noun if needed (for instance, if you want the persons' 
names in full caps instead of small caps).

Does your publisher really hinder you from putting the above macro in the 
preamble?

You can also use \textsc in LyX, that's in Edit->Text Style->Shape->Small Caps 
(which is different from Edit->Text Style->Misc->Noun).

As to \emph, this is semantic markup, defined in LaTeX2e. Its advantage 
compared to \textit is that it has italic correction.

Oh, and btw, *never* use \sc and \it instead of \textsc and \textit.

Jürgen

Re: \noun

[Bruce Pourciau]

Thanks Jürgen and Paul. I'm now in conversation with the journal.

They accept latex files and can build from them on their e-submission  
site a pdf that the author can view for approval, but this pdf is  
only for viewing -- it has all the figures lined up at the beginning,  
for example. And in my case, for some reason, it also did not show  
italic or small caps in the correct places. The journal is not  
typeset with latex, so they must have a way to go from a latex file  
to something in their format that's at least roughly accurate. In any  
case, they have to check the latex file to see where the figures go,  
so it seems to me they can also check it to see where \emph and \noun  
= \textsc are marking italic and small caps.


Bruce




On Jul 27, 2006, at 11:23 AM, Juergen Spitzmueller wrote:


Bruce Pourciau wrote:

Do I really have to go through the tex file and replace\emph
with \it and \noun with \sc?


No. \noun is semantic markup that uses a macro defined by LyX:

\newcommand{\noun}[1]{\textsc{#1}}

You see, it's really \textsc, but the advantage of semantic markup  
is that you
can easily redefine \noun if needed (for instance, if you want the  
persons'

names in full caps instead of small caps).

Does your publisher really hinder you from putting the above macro  
in the

preamble?

You can also use \textsc in LyX, that's in Edit->Text Style->Shape- 
>Small Caps

(which is different from Edit->Text Style->Misc->Noun).

As to \emph, this is semantic markup, defined in LaTeX2e. Its  
advantage

compared to \textit is that it has italic correction.

Oh, and btw, *never* use \sc and \it instead of \textsc and \textit.

Jürgen


Bruce Pourciau wrote:

I'll try to find out from the journal what they recommend to fix  
this problem. Thanks, Rich.





You might ask the journal whether they apply their own style files  
or macros and, if so, whether they happen to have a macro named  
\noun (which might be redefining the one LyX puts in the exported  
LaTeX).


/Paul

Re: error when noun style is not used in title environment

[Herbert Voss]

Ben Hourigan wrote:
I've been trying to get a quotation to appear on a separate page after 
the title page in a document I just started, and was frustrated to find 
that, while using what appeared to be the exact same series of commands, 
the new document returned errors when I attempted to view the PDF.

With any text between the date environment and the \mainmatter command 
or the next environment, Lyx would consider \mainmatter or the \part 
environment to be undefined commands.

After some experimentation I discovered an odd solution. If I used the 
noun style in the title environment, the following commands would be 
recognised correctly.

I'm curious to find out what's causing this behaviour. I've attached 
mimimal sample files. Works.lyx uses the noun style in the title 
environment, Error.lyx does not. Try to export to PDF using View  PDF 
(pdflatex).
the command \noun is not defined.
In preamble \let\noun\textsc solves the problem.
Herbert

--
http://TeXnik.de/
http://PSTricks.de/
ftp://ftp.dante.de/tex-archive/info/math/voss/Voss-Mathmode.pdf
http://www.dante.de/faq/de-tex-faq/
http://www.tex.ac.uk/cgi-bin/texfaq2html?introduction=yes
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass book
\begin_preamble
\hyphenation{fa-vour-a-ble Lo-gi-co-Phil-o-soph-ic-us there-of Trac-ta-tus  
vid-e-o-games Vid-e-o-games}
%
\fancyhead{}
\fancyfoot[C]{\thepage}
\fancyhead[CE]{\noun{\leftmark}}
\fancyhead[CO]{\noun{\rightmark}}
\renewcommand{\headrulewidth}{0pt}
\renewcommand{\footrulewidth}{0pt}
\let\noun\textsc
\end_preamble
\language british
\inputencoding auto
\fontscheme newcent
\graphics default
\paperfontsize 11
\spacing single 
\papersize a4paper
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle fancy

\layout Standard


\begin_inset ERT
status Collapsed

\layout Standard

\backslash 
frontmatter 
\end_inset 


\layout Title

Title
\layout Author

Author
\layout Date

Then -- 
\begin_inset ERT
status Collapsed

\layout Standard

\backslash 
today
\end_inset 


\layout Quote
\added_space_top vfill* \added_space_bottom vfill* 
Lorem ipsum dolor sit amet.
\layout Standard


\begin_inset ERT
status Collapsed

\layout Standard

\backslash 
mainmatter
\end_inset 


\layout Part

Title
\the_end

Re: error when noun style is not used in title environment

[Herbert Voss]

Ben Hourigan wrote:
I've been trying to get a quotation to appear on a separate page after 
the title page in a document I just started, and was frustrated to find 
that, while using what appeared to be the exact same series of commands, 
the new document returned errors when I attempted to view the PDF.

With any text between the date environment and the \mainmatter command 
or the next environment, Lyx would consider \mainmatter or the \part 
environment to be undefined commands.

After some experimentation I discovered an odd solution. If I used the 
noun style in the title environment, the following commands would be 
recognised correctly.

I'm curious to find out what's causing this behaviour. I've attached 
mimimal sample files. Works.lyx uses the noun style in the title 
environment, Error.lyx does not. Try to export to PDF using View  PDF 
(pdflatex).
the command \noun is not defined.
In preamble \let\noun\textsc solves the problem.
Herbert

--
http://TeXnik.de/
http://PSTricks.de/
ftp://ftp.dante.de/tex-archive/info/math/voss/Voss-Mathmode.pdf
http://www.dante.de/faq/de-tex-faq/
http://www.tex.ac.uk/cgi-bin/texfaq2html?introduction=yes
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass book
\begin_preamble
\hyphenation{fa-vour-a-ble Lo-gi-co-Phil-o-soph-ic-us there-of Trac-ta-tus  
vid-e-o-games Vid-e-o-games}
%
\fancyhead{}
\fancyfoot[C]{\thepage}
\fancyhead[CE]{\noun{\leftmark}}
\fancyhead[CO]{\noun{\rightmark}}
\renewcommand{\headrulewidth}{0pt}
\renewcommand{\footrulewidth}{0pt}
\let\noun\textsc
\end_preamble
\language british
\inputencoding auto
\fontscheme newcent
\graphics default
\paperfontsize 11
\spacing single 
\papersize a4paper
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle fancy

\layout Standard


\begin_inset ERT
status Collapsed

\layout Standard

\backslash 
frontmatter 
\end_inset 


\layout Title

Title
\layout Author

Author
\layout Date

Then -- 
\begin_inset ERT
status Collapsed

\layout Standard

\backslash 
today
\end_inset 


\layout Quote
\added_space_top vfill* \added_space_bottom vfill* 
Lorem ipsum dolor sit amet.
\layout Standard


\begin_inset ERT
status Collapsed

\layout Standard

\backslash 
mainmatter
\end_inset 


\layout Part

Title
\the_end

Re: error when noun style is not used in title environment

[Herbert Voss]

Ben Hourigan wrote:
I've been trying to get a quotation to appear on a separate page after 
the title page in a document I just started, and was frustrated to find 
that, while using what appeared to be the exact same series of commands, 
the new document returned errors when I attempted to view the PDF.

With any text between the date environment and the \mainmatter command 
or the next environment, Lyx would consider \mainmatter or the \part 
environment to be undefined commands.

After some experimentation I discovered an odd solution. If I used the 
noun style in the title environment, the following commands would be 
recognised correctly.

I'm curious to find out what's causing this behaviour. I've attached 
mimimal sample files. Works.lyx uses the noun style in the title 
environment, Error.lyx does not. Try to export to PDF using View > PDF 
(pdflatex).
the command \noun is not defined.
In preamble \let\noun\textsc solves the problem.
Herbert

--
http://TeXnik.de/
http://PSTricks.de/
ftp://ftp.dante.de/tex-archive/info/math/voss/Voss-Mathmode.pdf
http://www.dante.de/faq/de-tex-faq/
http://www.tex.ac.uk/cgi-bin/texfaq2html?introduction=yes
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass book
\begin_preamble
\hyphenation{fa-vour-a-ble Lo-gi-co-Phil-o-soph-ic-us there-of Trac-ta-tus  
vid-e-o-games Vid-e-o-games}
%
\fancyhead{}
\fancyfoot[C]{\thepage}
\fancyhead[CE]{\noun{\leftmark}}
\fancyhead[CO]{\noun{\rightmark}}
\renewcommand{\headrulewidth}{0pt}
\renewcommand{\footrulewidth}{0pt}
\let\noun\textsc
\end_preamble
\language british
\inputencoding auto
\fontscheme newcent
\graphics default
\paperfontsize 11
\spacing single 
\papersize a4paper
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle fancy

\layout Standard


\begin_inset ERT
status Collapsed

\layout Standard

\backslash 
frontmatter 
\end_inset 


\layout Title

Title
\layout Author

Author
\layout Date

Then -- 
\begin_inset ERT
status Collapsed

\layout Standard

\backslash 
today
\end_inset 


\layout Quote
\added_space_top vfill* \added_space_bottom vfill* 
Lorem ipsum dolor sit amet.
\layout Standard


\begin_inset ERT
status Collapsed

\layout Standard

\backslash 
mainmatter
\end_inset 


\layout Part

Title
\the_end

error when noun style is not used in title environment

[Ben Hourigan]

I've been trying to get a quotation to appear on a separate page after 
the title page in a document I just started, and was frustrated to find 
that, while using what appeared to be the exact same series of 
commands, the new document returned errors when I attempted to view the 
PDF.

With any text between the date environment and the \mainmatter command 
or the next environment, Lyx would consider \mainmatter or the \part 
environment to be undefined commands.

After some experimentation I discovered an odd solution. If I used the 
noun style in the title environment, the following commands would be 
recognised correctly.

I'm curious to find out what's causing this behaviour. I've attached 
mimimal sample files. Works.lyx uses the noun style in the title 
environment, Error.lyx does not. Try to export to PDF using View  PDF 
(pdflatex).

I'm using LyX/Aqua 1.3.5.
Ben


Error.lyx
Description: Binary data


Works.lyx
Description: Binary data

error when noun style is not used in title environment

[Ben Hourigan]

I've been trying to get a quotation to appear on a separate page after 
the title page in a document I just started, and was frustrated to find 
that, while using what appeared to be the exact same series of 
commands, the new document returned errors when I attempted to view the 
PDF.

With any text between the date environment and the \mainmatter command 
or the next environment, Lyx would consider \mainmatter or the \part 
environment to be undefined commands.

After some experimentation I discovered an odd solution. If I used the 
noun style in the title environment, the following commands would be 
recognised correctly.

I'm curious to find out what's causing this behaviour. I've attached 
mimimal sample files. Works.lyx uses the noun style in the title 
environment, Error.lyx does not. Try to export to PDF using View  PDF 
(pdflatex).

I'm using LyX/Aqua 1.3.5.
Ben


Error.lyx
Description: Binary data


Works.lyx
Description: Binary data

error when noun style is not used in title environment

[Ben Hourigan]

I've been trying to get a quotation to appear on a separate page after 
the title page in a document I just started, and was frustrated to find 
that, while using what appeared to be the exact same series of 
commands, the new document returned errors when I attempted to view the 
PDF.

With any text between the date environment and the \mainmatter command 
or the next environment, Lyx would consider \mainmatter or the \part 
environment to be undefined commands.

After some experimentation I discovered an odd solution. If I used the 
noun style in the title environment, the following commands would be 
recognised correctly.

I'm curious to find out what's causing this behaviour. I've attached 
mimimal sample files. Works.lyx uses the noun style in the title 
environment, Error.lyx does not. Try to export to PDF using View > PDF 
(pdflatex).

I'm using LyX/Aqua 1.3.5.
Ben


Error.lyx
Description: Binary data


Works.lyx
Description: Binary data

Re: Using Noun Style for SGML tags

[Chris Lale]

José Matos wrote:


  This trick will only work with latex, I was proposing a similar hack but for 
docbook, we would need to output the colour changes, something that we don't 
do now. This is the part that needs coding.

Thanks for the information. Sorry I cannot help with the coding but I am 
not proficient in C or C++. Perhaps in the future ...? Meanwhile, I will 
stick with ERT!

Cheers,

Chris.
--
:  ___   Chris Lale   [EMAIL PROTECTED]  :
: /   \   :
: | _/  My PC runs Debian GNU/Linux 3.0. :
: \  Robust, secure and free operating system + applications. :
:  \ Available at http://www.debian.org   :

Re: Using Noun Style for SGML tags

[Chris Lale]

José Matos wrote:


  This trick will only work with latex, I was proposing a similar hack but for 
docbook, we would need to output the colour changes, something that we don't 
do now. This is the part that needs coding.

Thanks for the information. Sorry I cannot help with the coding but I am 
not proficient in C or C++. Perhaps in the future ...? Meanwhile, I will 
stick with ERT!

Cheers,

Chris.
--
:  ___   Chris Lale   [EMAIL PROTECTED]  :
: /   \   :
: | _/  My PC runs Debian GNU/Linux 3.0. :
: \  Robust, secure and free operating system + applications. :
:  \ Available at http://www.debian.org   :

Re: Using Noun Style for SGML tags

[Chris Lale]

José Matos wrote:


  This trick will only work with latex, I was proposing a similar hack but for 
docbook, we would need to output the colour changes, something that we don't 
do now. This is the part that needs coding.

Thanks for the information. Sorry I cannot help with the coding but I am 
not proficient in C or C++. Perhaps in the future ...? Meanwhile, I will 
stick with ERT!

Cheers,

Chris.
--
:  ___   Chris Lale   <[EMAIL PROTECTED]>  :
: /   \   :
: | <_/  My PC runs Debian GNU/Linux 3.0. :
: \  Robust, secure and free operating system + applications. :
:  \ Available at http://www.debian.org   :

Re: Using Noun Style for SGML tags

[Chris Lale]

José Matos wrote:
 On Friday 06 December 2002 10:04, Chris Lale wrote:

I am using DocBook article (SGML)in Lyx 1.1.6fix4. I make much use of a
few inline SGML tags eg filenamesome text/filename.

   Instead of adding this kind of hacks I would prefer to work in the 
full
 solution, as it is easier to maintain in the long term. And the 
proper fix is
 to add support for styles in lyx.

   If you still want to make this work, I can give some tips where to 
look for.
 Actually you only need to change the code in one function, so it 
shouldn't be
 too hard.

If this means modifying text configuration files, yes please - I will
have a go. I am not proficient in C though.


   Now if you want to fake some styles we can use the colours, that 
clearly
 don't have any counterparts in docbook and use them for different 
styles. But
 this only shows how much we need real user defined styles in lyx.

I did try this (modified from the troubleshooters.com Linux Productivity
Magazine), but it did not work in 'DocBook article (SGML)':


Layout  LaTex Preamble...

% %%% Pseudo character styles indexed by color %%%
\usepackage{ifthen}
\providecommand{\textcolor}[2]{#2}
\renewcommand{\textcolor}[2]{%
\ifthenelse{\equal{#1}{blue}}{{filename{#2}/filename}}{}%  SGML
filename tags
\ifthenelse{\equal{#1}{magenta}}{{\large{\texttt{#2{}%Large text
\ifthenelse{\equal{#1}{magenta}\or\equal{#1}{blue}}{}{#2}%fallthrough
}


Here is the text in Lyx ('myfile' is blue and 'Large' is magenta):

	newbie test myfile
	Large text


This produced unaltered text when viewed in DVI.
With Export  DocBook, the SGML file contained no filename tags:
	para
	 newbie test myfile
	/para
	para
	 Large text
	/para


Also, the preamble was printed at the top of both the DVI and the SGML
documents.

If I change the document from 'DocBook article (SGML)' to 'article' and
view in DVI, the magenta text is in large type, and the preamble is not
printed at the top.

Any ideas?

Cheers,

Chris.
--
:  ___   Chris Lale   [EMAIL PROTECTED]  :
: /   \   :
: | _/  My PC runs Debian GNU/Linux 3.0. :
: \  Robust, secure and free operating system + applications. :
:  \ Available at http://www.debian.org   :

Re: Using Noun Style for SGML tags

[José Matos]

On Tuesday 10 December 2002 10:26, Chris Lale wrote:
 proper fix is to add support for styles in lyx.
   If you still want to make this work, I can give some tips where to
 look for.

  Actually you only need to change the code in one function, so it
 shouldn't be too hard.

 If this means modifying text configuration files, yes please - I will
 have a go. I am not proficient in C though.

  I was speaking of a C++ function, Buffer::simpleDocBookOnePar in 
src/buffer.C

 I did try this (modified from the troubleshooters.com Linux Productivity
 Magazine), but it did not work in 'DocBook article (SGML)':

 
 Layout  LaTex Preamble...

 % %%% Pseudo character styles indexed by color %%%
 \usepackage{ifthen}
 \providecommand{\textcolor}[2]{#2}
 \renewcommand{\textcolor}[2]{%
 \ifthenelse{\equal{#1}{blue}}{{filename{#2}/filename}}{}%  SGML
 filename tags
 \ifthenelse{\equal{#1}{magenta}}{{\large{\texttt{#2{}%Large text
 \ifthenelse{\equal{#1}{magenta}\or\equal{#1}{blue}}{}{#2}%fallthrough
 }

  This trick will only work with latex, I was proposing a similar hack but for 
docbook, we would need to output the colour changes, something that we don't 
do now. This is the part that needs coding.

[...]
 Any ideas?

 Cheers,

 Chris.

-- 
José Abílio

Re: Using Noun Style for SGML tags

[Chris Lale]

José Matos wrote:
 On Friday 06 December 2002 10:04, Chris Lale wrote:

I am using DocBook article (SGML)in Lyx 1.1.6fix4. I make much use of a
few inline SGML tags eg filenamesome text/filename.

   Instead of adding this kind of hacks I would prefer to work in the 
full
 solution, as it is easier to maintain in the long term. And the 
proper fix is
 to add support for styles in lyx.

   If you still want to make this work, I can give some tips where to 
look for.
 Actually you only need to change the code in one function, so it 
shouldn't be
 too hard.

If this means modifying text configuration files, yes please - I will
have a go. I am not proficient in C though.


   Now if you want to fake some styles we can use the colours, that 
clearly
 don't have any counterparts in docbook and use them for different 
styles. But
 this only shows how much we need real user defined styles in lyx.

I did try this (modified from the troubleshooters.com Linux Productivity
Magazine), but it did not work in 'DocBook article (SGML)':


Layout  LaTex Preamble...

% %%% Pseudo character styles indexed by color %%%
\usepackage{ifthen}
\providecommand{\textcolor}[2]{#2}
\renewcommand{\textcolor}[2]{%
\ifthenelse{\equal{#1}{blue}}{{filename{#2}/filename}}{}%  SGML
filename tags
\ifthenelse{\equal{#1}{magenta}}{{\large{\texttt{#2{}%Large text
\ifthenelse{\equal{#1}{magenta}\or\equal{#1}{blue}}{}{#2}%fallthrough
}


Here is the text in Lyx ('myfile' is blue and 'Large' is magenta):

	newbie test myfile
	Large text


This produced unaltered text when viewed in DVI.
With Export  DocBook, the SGML file contained no filename tags:
	para
	 newbie test myfile
	/para
	para
	 Large text
	/para


Also, the preamble was printed at the top of both the DVI and the SGML
documents.

If I change the document from 'DocBook article (SGML)' to 'article' and
view in DVI, the magenta text is in large type, and the preamble is not
printed at the top.

Any ideas?

Cheers,

Chris.
--
:  ___   Chris Lale   [EMAIL PROTECTED]  :
: /   \   :
: | _/  My PC runs Debian GNU/Linux 3.0. :
: \  Robust, secure and free operating system + applications. :
:  \ Available at http://www.debian.org   :

Re: Using Noun Style for SGML tags

[José Matos]

On Tuesday 10 December 2002 10:26, Chris Lale wrote:
 proper fix is to add support for styles in lyx.
   If you still want to make this work, I can give some tips where to
 look for.

  Actually you only need to change the code in one function, so it
 shouldn't be too hard.

 If this means modifying text configuration files, yes please - I will
 have a go. I am not proficient in C though.

  I was speaking of a C++ function, Buffer::simpleDocBookOnePar in 
src/buffer.C

 I did try this (modified from the troubleshooters.com Linux Productivity
 Magazine), but it did not work in 'DocBook article (SGML)':

 
 Layout  LaTex Preamble...

 % %%% Pseudo character styles indexed by color %%%
 \usepackage{ifthen}
 \providecommand{\textcolor}[2]{#2}
 \renewcommand{\textcolor}[2]{%
 \ifthenelse{\equal{#1}{blue}}{{filename{#2}/filename}}{}%  SGML
 filename tags
 \ifthenelse{\equal{#1}{magenta}}{{\large{\texttt{#2{}%Large text
 \ifthenelse{\equal{#1}{magenta}\or\equal{#1}{blue}}{}{#2}%fallthrough
 }

  This trick will only work with latex, I was proposing a similar hack but for 
docbook, we would need to output the colour changes, something that we don't 
do now. This is the part that needs coding.

[...]
 Any ideas?

 Cheers,

 Chris.

-- 
José Abílio

Re: Using Noun Style for SGML tags

[Chris Lale]

José Matos wrote:
> On Friday 06 December 2002 10:04, Chris Lale wrote:
>
>>I am using DocBook article (SGML)in Lyx 1.1.6fix4. I make much use of a
>>few inline SGML tags eg some text.
>
>   Instead of adding this kind of hacks I would prefer to work in the 
full
> solution, as it is easier to maintain in the long term. And the 
proper fix is
> to add support for styles in lyx.
>
>   If you still want to make this work, I can give some tips where to 
look for.
> Actually you only need to change the code in one function, so it 
shouldn't be
> too hard.

If this means modifying text configuration files, yes please - I will
have a go. I am not proficient in C though.

>
>   Now if you want to fake some styles we can use the colours, that 
clearly
> don't have any counterparts in docbook and use them for different 
styles. But
> this only shows how much we need real user defined styles in lyx.

I did try this (modified from the troubleshooters.com Linux Productivity
Magazine), but it did not work in 'DocBook article (SGML)':


Layout > LaTex Preamble...

% %%% Pseudo character styles indexed by color %%%
\usepackage{ifthen}
\providecommand{\textcolor}[2]{#2}
\renewcommand{\textcolor}[2]{%
\ifthenelse{\equal{#1}{blue}}{{{#2}}}{}%  SGML
filename tags
\ifthenelse{\equal{#1}{magenta}}{{\large{\texttt{#2{}%Large text
\ifthenelse{\equal{#1}{magenta}\or\equal{#1}{blue}}{}{#2}%fallthrough
}


Here is the text in Lyx ('myfile' is blue and 'Large' is magenta):

	newbie test myfile
	Large text


This produced unaltered text when viewed in DVI.
With Export > DocBook, the SGML file contained no  tags:
	
	 newbie test myfile
	
	
	 Large text
	


Also, the preamble was printed at the top of both the DVI and the SGML
documents.

If I change the document from 'DocBook article (SGML)' to 'article' and
view in DVI, the magenta text is in large type, and the preamble is not
printed at the top.

Any ideas?

Cheers,

Chris.
--
:  ___   Chris Lale   <[EMAIL PROTECTED]>  :
: /   \   :
: | <_/  My PC runs Debian GNU/Linux 3.0. :
: \  Robust, secure and free operating system + applications. :
:  \ Available at http://www.debian.org   :

Re: Using Noun Style for SGML tags

[José Matos]

On Tuesday 10 December 2002 10:26, Chris Lale wrote:
>> proper fix is to add support for styles in lyx.
>>   If you still want to make this work, I can give some tips where to
>> look for.
>>
>>  Actually you only need to change the code in one function, so it
>> shouldn't be too hard.
>
> If this means modifying text configuration files, yes please - I will
> have a go. I am not proficient in C though.

  I was speaking of a C++ function, Buffer::simpleDocBookOnePar in 
src/buffer.C

> I did try this (modified from the troubleshooters.com Linux Productivity
> Magazine), but it did not work in 'DocBook article (SGML)':
>
> 
> Layout > LaTex Preamble...
>
> % %%% Pseudo character styles indexed by color %%%
> \usepackage{ifthen}
> \providecommand{\textcolor}[2]{#2}
> \renewcommand{\textcolor}[2]{%
> \ifthenelse{\equal{#1}{blue}}{{{#2}}}{}%  SGML
> filename tags
> \ifthenelse{\equal{#1}{magenta}}{{\large{\texttt{#2{}%Large text
> \ifthenelse{\equal{#1}{magenta}\or\equal{#1}{blue}}{}{#2}%fallthrough
> }

  This trick will only work with latex, I was proposing a similar hack but for 
docbook, we would need to output the colour changes, something that we don't 
do now. This is the part that needs coding.

[...]
> Any ideas?

> Cheers,
>
> Chris.

-- 
José Abílio

Using Noun Style for SGML tags

[Chris Lale]

I am using DocBook article (SGML)in Lyx 1.1.6fix4. I make much use of a 
few inline SGML tags eg filenamesome text/filename. The  ...  tags 
are in red text. I would like to avoid using the red tags by redefining 
Styles in the preamble. Here is the most complex change I wish to make:

Layout  Noun Style
Render as Bold and Typewriter (without Small Caps) in Lyx, DVI, PDF.
Render as filenamesome text/filename when exported to DocBook.

If I can find out how do this, I should be able to redefine other Styles 
to render other SGML tags.

I would be grateful for any suggestions.

Thanks,

Chris.
--
:  ___   Chris Lale   [EMAIL PROTECTED]  :
: /   \   :
: | _/  My PC runs Debian GNU/Linux 3.0. :
: \  Robust, secure and free operating system + applications. :
:  \ Available at http://www.debian.org   :

Re: Using Noun Style for SGML tags

[José Matos]

On Friday 06 December 2002 10:04, Chris Lale wrote:
 I am using DocBook article (SGML)in Lyx 1.1.6fix4. I make much use of a
 few inline SGML tags eg filenamesome text/filename. The  ...  tags
 are in red text. I would like to avoid using the red tags by redefining
 Styles in the preamble. Here is the most complex change I wish to make:

 Layout  Noun Style
 Render as Bold and Typewriter (without Small Caps) in Lyx, DVI, PDF.
 Render as filenamesome text/filename when exported to DocBook.

 If I can find out how do this, I should be able to redefine other Styles
 to render other SGML tags.

  Similar to that I planned to redirect typewriter font to literal. But where 
the meaning seems obvious.
  Certainly we can define Small Caps to mean filename, but this would be only 
a hack.

  Instead of adding this kind of hacks I would prefer to work in the full 
solution, as it is easier to maintain in the long term. And the proper fix is 
to add support for styles in lyx.

  If you still want to make this work, I can give some tips where to look for. 
Actually you only need to change the code in one function, so it shouldn't be 
too hard.

  Now if you want to fake some styles we can use the colours, that clearly 
don't have any counterparts in docbook and use them for different styles. But 
this only shows how much we need real user defined styles in lyx.

 I would be grateful for any suggestions.

  I hope this helps,

 Thanks,

 Chris.

-- 
José Abílio

Using Noun Style for SGML tags

[Chris Lale]

I am using DocBook article (SGML)in Lyx 1.1.6fix4. I make much use of a 
few inline SGML tags eg filenamesome text/filename. The  ...  tags 
are in red text. I would like to avoid using the red tags by redefining 
Styles in the preamble. Here is the most complex change I wish to make:

Layout  Noun Style
Render as Bold and Typewriter (without Small Caps) in Lyx, DVI, PDF.
Render as filenamesome text/filename when exported to DocBook.

If I can find out how do this, I should be able to redefine other Styles 
to render other SGML tags.

I would be grateful for any suggestions.

Thanks,

Chris.
--
:  ___   Chris Lale   [EMAIL PROTECTED]  :
: /   \   :
: | _/  My PC runs Debian GNU/Linux 3.0. :
: \  Robust, secure and free operating system + applications. :
:  \ Available at http://www.debian.org   :

Re: Using Noun Style for SGML tags

[José Matos]

On Friday 06 December 2002 10:04, Chris Lale wrote:
 I am using DocBook article (SGML)in Lyx 1.1.6fix4. I make much use of a
 few inline SGML tags eg filenamesome text/filename. The  ...  tags
 are in red text. I would like to avoid using the red tags by redefining
 Styles in the preamble. Here is the most complex change I wish to make:

 Layout  Noun Style
 Render as Bold and Typewriter (without Small Caps) in Lyx, DVI, PDF.
 Render as filenamesome text/filename when exported to DocBook.

 If I can find out how do this, I should be able to redefine other Styles
 to render other SGML tags.

  Similar to that I planned to redirect typewriter font to literal. But where 
the meaning seems obvious.
  Certainly we can define Small Caps to mean filename, but this would be only 
a hack.

  Instead of adding this kind of hacks I would prefer to work in the full 
solution, as it is easier to maintain in the long term. And the proper fix is 
to add support for styles in lyx.

  If you still want to make this work, I can give some tips where to look for. 
Actually you only need to change the code in one function, so it shouldn't be 
too hard.

  Now if you want to fake some styles we can use the colours, that clearly 
don't have any counterparts in docbook and use them for different styles. But 
this only shows how much we need real user defined styles in lyx.

 I would be grateful for any suggestions.

  I hope this helps,

 Thanks,

 Chris.

-- 
José Abílio

Using Noun Style for SGML tags

[Chris Lale]

I am using DocBook article (SGML)in Lyx 1.1.6fix4. I make much use of a 
few inline SGML tags eg some text. The < ... > tags 
are in red text. I would like to avoid using the red tags by redefining 
Styles in the preamble. Here is the most complex change I wish to make:

Layout > Noun Style
Render as Bold and Typewriter (without Small Caps) in Lyx, DVI, PDF.
Render as some text when exported to DocBook.

If I can find out how do this, I should be able to redefine other Styles 
to render other SGML tags.

I would be grateful for any suggestions.

Thanks,

Chris.
--
:  ___   Chris Lale   <[EMAIL PROTECTED]>  :
: /   \   :
: | <_/  My PC runs Debian GNU/Linux 3.0. :
: \  Robust, secure and free operating system + applications. :
:  \ Available at http://www.debian.org   :

Re: Using Noun Style for SGML tags

[José Matos]

On Friday 06 December 2002 10:04, Chris Lale wrote:
> I am using DocBook article (SGML)in Lyx 1.1.6fix4. I make much use of a
> few inline SGML tags eg some text. The < ... > tags
> are in red text. I would like to avoid using the red tags by redefining
> Styles in the preamble. Here is the most complex change I wish to make:
>
> Layout > Noun Style
> Render as Bold and Typewriter (without Small Caps) in Lyx, DVI, PDF.
> Render as some text when exported to DocBook.
>
> If I can find out how do this, I should be able to redefine other Styles
> to render other SGML tags.

  Similar to that I planned to redirect typewriter font to literal. But where 
the meaning seems obvious.
  Certainly we can define Small Caps to mean filename, but this would be only 
a hack.

  Instead of adding this kind of hacks I would prefer to work in the full 
solution, as it is easier to maintain in the long term. And the proper fix is 
to add support for styles in lyx.

  If you still want to make this work, I can give some tips where to look for. 
Actually you only need to change the code in one function, so it shouldn't be 
too hard.

  Now if you want to fake some styles we can use the colours, that clearly 
don't have any counterparts in docbook and use them for different styles. But 
this only shows how much we need real user defined styles in lyx.

> I would be grateful for any suggestions.

  I hope this helps,

> Thanks,
>
> Chris.

-- 
José Abílio

Bug (?) with noun style in titles

[Emanuele Gissi Alessia Franceschi]

Hi,

I am writing my thesis in LyX.
I use the class "book (koma-script)".
I have got some names in the chapter and section titles.
So I set them to "noun style" on. In LyX they show well.
But when I look at the postscript output they don't retain the style and show
themselves as the other chapter and section title text.
In subsections and below the nouns show themselves properly.

I think the problem is due to the underling LaTeX class.
How to overcome this problem? can we consider it a LyX bug?

However, thank you as usual.

Emanuele
-- 
Emanuele Gissi  Alessia Franceschi
via Damiano Chiesa 20/B
60123 Ancona - Italia
tel: 0039 071 32979 - email: [EMAIL PROTECTED]
fax: 0039 071 220.2256

"L'imagination, ce n'est pas le mensonge"
[Daniel Pennac - Messieurs les enfants, ed. Gallimard, Paris, 1997]