New Feature Request: Chapter Contents

2013-10-06 Thread Mark Horton
Hi Developers

It would make navigation a lot easier for large documents if we had the
the ability to generate a contents of Chapters at the start.

Plus a more detailed contents page at the start of each Chapter. 


Best Regards

Mark Horton



Re: New Feature Request: Chapter Contents

2013-10-06 Thread Richard Heck

On 10/06/2013 07:33 AM, Mark Horton wrote:

Hi Developers

It would make navigation a lot easier for large documents if we had the
the ability to generate a contents of Chapters at the start.

Plus a more detailed contents page at the start of each Chapter.


This is a LaTeX issue, first and foremost. It's easy to get only the 
chapters in the TOC initially. (See Document Settings Numbering and 
TOC). It's getting the TOCs for each chapter that is the issue. But I 
believe there are LaTeX packages that will do this. Go to CTAN.org and 
search for them, or try googling. If you can find it, then, at a bare 
minimum, you could do this with ERT, and you can also file an 
enhancement request for native support for the package.


Richard



Re: Cannot export Math manual using XeTeX

2013-10-06 Thread Guenter Milde
On 2013-10-03, Scott Kostyshak wrote:
 On Thu, Oct 3, 2013 at 4:28 PM, Guenter Milde mi...@users.sf.net wrote:
 On 2013-10-03, Scott Kostyshak wrote:
 On Thu, Oct 3, 2013 at 5:02 AM, Guenter Milde mi...@users.sf.net wrote:
 On 2013-10-03, Scott Kostyshak wrote:
 Thanks for the confirmation. I started a thread on lyx-devel.
 Hopefully there's an easy way to have pdfTeX and XeTeX working. Note
 that if I remove the following lines from the preamble, export with
 XeTeX
 works fine (but pdfTeX is broken):

 \DeclareInputText{176}{\ifmmode^\circ\else\textdegree\fi}
 \DeclareInputText{183}{\ifmmode\cdot\else\textperiodcentered\fi}

 There is a simple fix: move the offending lines into the

 \ifpdf
 \fi

 block.

 However, the right way is to remove the lines as well as the section
 in the guide, because it is no longer true. Since several versions,
 LYXDIR/unicodesymbols contains the required definitions for text and
 math mode.

 I prefer the right way. So you suggest to remove the two
 DeclareInputText commands and to remove all of the section
 Miscellaneous special Characters ?

 After I do that, I get errors because of the € symbol. After I remove
 those occurrences, XeTeX and pdfTeX both export fine. There is an
 entry in unicodesymbols for the euro. Is this a different euro?

 The \texteuro macro is provided by the textcomp package.

 A quick and dirty fix would be to set the force flag so that the textcomp
 package is auto-loaded. However, this is an overkill as this would also
 replace the Euro (€) character with the \texteuro macro which is not
 required for the TeX input encodings
 utf8, ansinew, cp1250, cp1252, cp1257, cp858, latin10, and latin9

 A force-preamble flag that only forces loading the preamble code without
 forcing the replacement could solve the issue. For the textcomp feature
 this regards the characters
 # recognized with 'utf8', if textcomp is loaded
 textcomp = {
 # Latin-1 Supplement
 0x00a2: ur'\textcent{}',  # ¢ CENT SIGN
 0x00a4: ur'\textcurrency{}',  # ¤ CURRENCY SYMBOL
 0x00a5: ur'\textyen{}',   # ¥ YEN SIGN
 0x00a6: ur'\textbrokenbar{}', # ¦ BROKEN BAR
 0x00a7: ur'\textsection{}',   # § SECTION SIGN
 0x00a8: ur'\textasciidieresis{}', # ¨ DIAERESIS
 0x00a9: ur'\textcopyright{}', # © COPYRIGHT SIGN
 0x00aa: ur'\textordfeminine{}',   # ª FEMININE ORDINAL INDICATOR
 0x00ac: ur'\textlnot{}',  # ¬ NOT SIGN
 0x00ae: ur'\textregistered{}',# ® REGISTERED SIGN
 0x00af: ur'\textasciimacron{}',   # ¯ MACRON
 0x00b0: ur'\textdegree{}',# ° DEGREE SIGN
 0x00b1: ur'\textpm{}',# ± PLUS-MINUS SIGN
 0x00b2: ur'\texttwosuperior{}',   # ² SUPERSCRIPT TWO
 0x00b3: ur'\textthreesuperior{}', # ³ SUPERSCRIPT THREE
 0x00b4: ur'\textasciiacute{}',# ´ ACUTE ACCENT
 0x00b5: ur'\textmu{}',# µ MICRO SIGN
 0x00b6: ur'\textparagraph{}', # ¶ PILCROW SIGN # != \textpilcrow
 0x00b9: ur'\textonesuperior{}',   # ¹ SUPERSCRIPT ONE
 0x00ba: ur'\textordmasculine{}',  # º MASCULINE ORDINAL INDICATOR
 0x00bc: ur'\textonequarter{}',# 1/4 FRACTION
 0x00bd: ur'\textonehalf{}',   # 1/2 FRACTION
 0x00be: ur'\textthreequarters{}', # 3/4 FRACTION
 0x00d7: ur'\texttimes{}', # × MULTIPLICATION SIGN
 0x00f7: ur'\textdiv{}',   # ÷ DIVISION SIGN
 # others
 0x0192: ur'\textflorin{}',# LATIN SMALL LETTER F WITH HOOK
 0x02b9: ur'\textasciiacute{}',# MODIFIER LETTER PRIME
 0x02ba: ur'\textacutedbl{}',  # MODIFIER LETTER DOUBLE PRIME
 0x2016: ur'\textbardbl{}',# DOUBLE VERTICAL LINE
 0x2022: ur'\textbullet{}',# BULLET
 0x2032: ur'\textasciiacute{}',# PRIME
 0x2033: ur'\textacutedbl{}',  # DOUBLE PRIME
 0x2035: ur'\textasciigrave{}',# REVERSED PRIME
 0x2036: ur'\textgravedbl{}',  # REVERSED DOUBLE PRIME
 0x203b: ur'\textreferencemark{}', # REFERENCE MARK
 0x203d: ur'\textinterrobang{}',   # INTERROBANG
 0x2044: ur'\textfractionsolidus{}', # FRACTION SLASH
 0x2045: ur'\textlquill{}',# LEFT SQUARE BRACKET WITH QUILL
 0x2046: ur'\textrquill{}',# RIGHT SQUARE BRACKET WITH QUILL
 0x2052: ur'\textdiscount{}',  # COMMERCIAL MINUS SIGN
 0x20a1: ur'\textcolonmonetary{}', # COLON SIGN
 0x20a3: ur'\textfrenchfranc{}',   # FRENCH FRANC SIGN
 0x20a4: ur'\textlira{}',  # LIRA SIGN
 0x20a6: ur'\textnaira{}', # NAIRA SIGN
 0x20a9: ur'\textwon{}',   # WON SIGN
 0x20ab: ur'\textdong{}',  # DONG SIGN
 0x20ac: ur'\texteuro{}',  # EURO SIGN
 0x20b1: ur'\textpeso{}',  # PESO SIGN
 0x20b2: ur'\textguarani{}',   # GUARANI SIGN
 

Re: New Feature Request: Chapter Contents

2013-10-06 Thread Andrew Parsloe

On 7/10/2013 4:49 a.m., Richard Heck wrote:

On 10/06/2013 07:33 AM, Mark Horton wrote:

Hi Developers

It would make navigation a lot easier for large documents if we had the
the ability to generate a contents of Chapters at the start.

Plus a more detailed contents page at the start of each Chapter.


This is a LaTeX issue, first and foremost. It's easy to get only the
chapters in the TOC initially. (See Document Settings Numbering and
TOC). It's getting the TOCs for each chapter that is the issue. But I
believe there are LaTeX packages that will do this. Go to CTAN.org and
search for them, or try googling. If you can find it, then, at a bare
minimum, you could do this with ERT, and you can also file an
enhancement request for native support for the package.

Richard



I've used the LaTeX minitoc package successfully with LyX for a large 
book (600 pages). It creates a table of contents for each chapter, 
inserted at the start of the chapter. I restricted the main TOC at the 
start of the book to section level, but each chapter TOC was to 
subsubsection level. Each chapter has \minitoc in ERT after the chapter 
heading, but that's all, so ERT use is minimal. The preamble to the 
master document (each chapter is a child document  has nothing in the 
preamble) has


\usepackage[tight]{minitoc}
\setcounter{minitocdepth}{3}
\setlength{\mtcindent}{24pt}
\renewcommand{\mtcfont}{\small\rm}
\renewcommand{\mtcSfont}{\small\bf}
\renewcommand{\mtcSSSfont}{\footnotesize\it}
\renewcommand{\mtctitle}{}

which shows the kind of tailoring to individual whims that is possible.

Andrew


Re: Cannot export Math manual using XeTeX

2013-10-06 Thread Scott Kostyshak
On Sun, Oct 6, 2013 at 11:57 AM, Guenter Milde mi...@users.sf.net wrote:
 On 2013-10-03, Scott Kostyshak wrote:
 On Thu, Oct 3, 2013 at 4:28 PM, Guenter Milde mi...@users.sf.net wrote:
 On 2013-10-03, Scott Kostyshak wrote:
 On Thu, Oct 3, 2013 at 5:02 AM, Guenter Milde mi...@users.sf.net wrote:
 On 2013-10-03, Scott Kostyshak wrote:
 Thanks for the confirmation. I started a thread on lyx-devel.
 Hopefully there's an easy way to have pdfTeX and XeTeX working. Note
 that if I remove the following lines from the preamble, export with
 XeTeX
 works fine (but pdfTeX is broken):

 \DeclareInputText{176}{\ifmmode^\circ\else\textdegree\fi}
 \DeclareInputText{183}{\ifmmode\cdot\else\textperiodcentered\fi}

 There is a simple fix: move the offending lines into the

 \ifpdf
 \fi

 block.

 However, the right way is to remove the lines as well as the section
 in the guide, because it is no longer true. Since several versions,
 LYXDIR/unicodesymbols contains the required definitions for text and
 math mode.

 I prefer the right way. So you suggest to remove the two
 DeclareInputText commands and to remove all of the section
 Miscellaneous special Characters ?

 After I do that, I get errors because of the € symbol. After I remove
 those occurrences, XeTeX and pdfTeX both export fine. There is an
 entry in unicodesymbols for the euro. Is this a different euro?

 The \texteuro macro is provided by the textcomp package.

 A quick and dirty fix would be to set the force flag so that the textcomp
 package is auto-loaded. However, this is an overkill as this would also
 replace the Euro (€) character with the \texteuro macro which is not
 required for the TeX input encodings
 utf8, ansinew, cp1250, cp1252, cp1257, cp858, latin10, and latin9

 A force-preamble flag that only forces loading the preamble code without
 forcing the replacement could solve the issue. For the textcomp feature
 this regards the characters
 # recognized with 'utf8', if textcomp is loaded
 textcomp = {
 # Latin-1 Supplement
 0x00a2: ur'\textcent{}',  # ¢ CENT SIGN
 0x00a4: ur'\textcurrency{}',  # ¤ CURRENCY SYMBOL
 0x00a5: ur'\textyen{}',   # ¥ YEN SIGN
 0x00a6: ur'\textbrokenbar{}', # ¦ BROKEN BAR
 0x00a7: ur'\textsection{}',   # § SECTION SIGN
 0x00a8: ur'\textasciidieresis{}', # ¨ DIAERESIS
 0x00a9: ur'\textcopyright{}', # © COPYRIGHT SIGN
 0x00aa: ur'\textordfeminine{}',   # ª FEMININE ORDINAL INDICATOR
 0x00ac: ur'\textlnot{}',  # ¬ NOT SIGN
 0x00ae: ur'\textregistered{}',# ® REGISTERED SIGN
 0x00af: ur'\textasciimacron{}',   # ¯ MACRON
 0x00b0: ur'\textdegree{}',# ° DEGREE SIGN
 0x00b1: ur'\textpm{}',# ± PLUS-MINUS SIGN
 0x00b2: ur'\texttwosuperior{}',   # ² SUPERSCRIPT TWO
 0x00b3: ur'\textthreesuperior{}', # ³ SUPERSCRIPT THREE
 0x00b4: ur'\textasciiacute{}',# ´ ACUTE ACCENT
 0x00b5: ur'\textmu{}',# µ MICRO SIGN
 0x00b6: ur'\textparagraph{}', # ¶ PILCROW SIGN # != \textpilcrow
 0x00b9: ur'\textonesuperior{}',   # ¹ SUPERSCRIPT ONE
 0x00ba: ur'\textordmasculine{}',  # º MASCULINE ORDINAL INDICATOR
 0x00bc: ur'\textonequarter{}',# 1/4 FRACTION
 0x00bd: ur'\textonehalf{}',   # 1/2 FRACTION
 0x00be: ur'\textthreequarters{}', # 3/4 FRACTION
 0x00d7: ur'\texttimes{}', # × MULTIPLICATION SIGN
 0x00f7: ur'\textdiv{}',   # ÷ DIVISION SIGN
 # others
 0x0192: ur'\textflorin{}',# LATIN SMALL LETTER F WITH HOOK
 0x02b9: ur'\textasciiacute{}',# MODIFIER LETTER PRIME
 0x02ba: ur'\textacutedbl{}',  # MODIFIER LETTER DOUBLE PRIME
 0x2016: ur'\textbardbl{}',# DOUBLE VERTICAL LINE
 0x2022: ur'\textbullet{}',# BULLET
 0x2032: ur'\textasciiacute{}',# PRIME
 0x2033: ur'\textacutedbl{}',  # DOUBLE PRIME
 0x2035: ur'\textasciigrave{}',# REVERSED PRIME
 0x2036: ur'\textgravedbl{}',  # REVERSED DOUBLE PRIME
 0x203b: ur'\textreferencemark{}', # REFERENCE MARK
 0x203d: ur'\textinterrobang{}',   # INTERROBANG
 0x2044: ur'\textfractionsolidus{}', # FRACTION SLASH
 0x2045: ur'\textlquill{}',# LEFT SQUARE BRACKET WITH QUILL
 0x2046: ur'\textrquill{}',# RIGHT SQUARE BRACKET WITH QUILL
 0x2052: ur'\textdiscount{}',  # COMMERCIAL MINUS SIGN
 0x20a1: ur'\textcolonmonetary{}', # COLON SIGN
 0x20a3: ur'\textfrenchfranc{}',   # FRENCH FRANC SIGN
 0x20a4: ur'\textlira{}',  # LIRA SIGN
 0x20a6: ur'\textnaira{}', # NAIRA SIGN
 0x20a9: ur'\textwon{}',   # WON SIGN
 0x20ab: ur'\textdong{}',  # DONG SIGN
 0x20ac: ur'\texteuro{}',  # EURO SIGN
 0x20b1: ur'\textpeso{}',   

Re: New Feature Request: Chapter Contents

2013-10-06 Thread Richard Heck

On 10/06/2013 07:33 AM, Mark Horton wrote:

 Hi Developers

 It would make navigation a lot easier for large documents if we had the
 the ability to generate a contents of Chapters at the start.

 Plus a more detailed contents page at the start of each Chapter.

This is a LaTeX issue, first and foremost. It's easy to get only the 
chapters in the TOC initially. (See Document Settings Numbering and 
TOC). It's getting the TOCs for each chapter that is the issue. But I 
believe there are LaTeX packages that will do this. Go to CTAN.org 
and search for them, or try googling. If you can find it, then, at a 
bare minimum, you could do this with ERT, and you can also file an 
enhancement request for native support for the package.




Thanks for the prompt reply.

I have found a package to do the job called Minitoc. Unfortunately 
being an ignorant beginner in this field  I don't know how to Install 
it  and make it work from Latex.


What OS are you using? There's probably a Package Manager of some sort 
you can use to install the package.


Andrew's instructions on how to use minitoc can be explained in more 
detail once we have the package installed.


Richard

PS Keep replies on the list, in case someone else has similar questions.



New Feature Request: Chapter Contents

2013-10-06 Thread Mark Horton
Hi Developers

It would make navigation a lot easier for large documents if we had the
the ability to generate a contents of Chapters at the start.

Plus a more detailed contents page at the start of each Chapter. 


Best Regards

Mark Horton



Re: New Feature Request: Chapter Contents

2013-10-06 Thread Richard Heck

On 10/06/2013 07:33 AM, Mark Horton wrote:

Hi Developers

It would make navigation a lot easier for large documents if we had the
the ability to generate a contents of Chapters at the start.

Plus a more detailed contents page at the start of each Chapter.


This is a LaTeX issue, first and foremost. It's easy to get only the 
chapters in the TOC initially. (See Document Settings Numbering and 
TOC). It's getting the TOCs for each chapter that is the issue. But I 
believe there are LaTeX packages that will do this. Go to CTAN.org and 
search for them, or try googling. If you can find it, then, at a bare 
minimum, you could do this with ERT, and you can also file an 
enhancement request for native support for the package.


Richard



Re: Cannot export Math manual using XeTeX

2013-10-06 Thread Guenter Milde
On 2013-10-03, Scott Kostyshak wrote:
 On Thu, Oct 3, 2013 at 4:28 PM, Guenter Milde mi...@users.sf.net wrote:
 On 2013-10-03, Scott Kostyshak wrote:
 On Thu, Oct 3, 2013 at 5:02 AM, Guenter Milde mi...@users.sf.net wrote:
 On 2013-10-03, Scott Kostyshak wrote:
 Thanks for the confirmation. I started a thread on lyx-devel.
 Hopefully there's an easy way to have pdfTeX and XeTeX working. Note
 that if I remove the following lines from the preamble, export with
 XeTeX
 works fine (but pdfTeX is broken):

 \DeclareInputText{176}{\ifmmode^\circ\else\textdegree\fi}
 \DeclareInputText{183}{\ifmmode\cdot\else\textperiodcentered\fi}

 There is a simple fix: move the offending lines into the

 \ifpdf
 \fi

 block.

 However, the right way is to remove the lines as well as the section
 in the guide, because it is no longer true. Since several versions,
 LYXDIR/unicodesymbols contains the required definitions for text and
 math mode.

 I prefer the right way. So you suggest to remove the two
 DeclareInputText commands and to remove all of the section
 Miscellaneous special Characters ?

 After I do that, I get errors because of the € symbol. After I remove
 those occurrences, XeTeX and pdfTeX both export fine. There is an
 entry in unicodesymbols for the euro. Is this a different euro?

 The \texteuro macro is provided by the textcomp package.

 A quick and dirty fix would be to set the force flag so that the textcomp
 package is auto-loaded. However, this is an overkill as this would also
 replace the Euro (€) character with the \texteuro macro which is not
 required for the TeX input encodings
 utf8, ansinew, cp1250, cp1252, cp1257, cp858, latin10, and latin9

 A force-preamble flag that only forces loading the preamble code without
 forcing the replacement could solve the issue. For the textcomp feature
 this regards the characters
 # recognized with 'utf8', if textcomp is loaded
 textcomp = {
 # Latin-1 Supplement
 0x00a2: ur'\textcent{}',  # ¢ CENT SIGN
 0x00a4: ur'\textcurrency{}',  # ¤ CURRENCY SYMBOL
 0x00a5: ur'\textyen{}',   # ¥ YEN SIGN
 0x00a6: ur'\textbrokenbar{}', # ¦ BROKEN BAR
 0x00a7: ur'\textsection{}',   # § SECTION SIGN
 0x00a8: ur'\textasciidieresis{}', # ¨ DIAERESIS
 0x00a9: ur'\textcopyright{}', # © COPYRIGHT SIGN
 0x00aa: ur'\textordfeminine{}',   # ª FEMININE ORDINAL INDICATOR
 0x00ac: ur'\textlnot{}',  # ¬ NOT SIGN
 0x00ae: ur'\textregistered{}',# ® REGISTERED SIGN
 0x00af: ur'\textasciimacron{}',   # ¯ MACRON
 0x00b0: ur'\textdegree{}',# ° DEGREE SIGN
 0x00b1: ur'\textpm{}',# ± PLUS-MINUS SIGN
 0x00b2: ur'\texttwosuperior{}',   # ² SUPERSCRIPT TWO
 0x00b3: ur'\textthreesuperior{}', # ³ SUPERSCRIPT THREE
 0x00b4: ur'\textasciiacute{}',# ´ ACUTE ACCENT
 0x00b5: ur'\textmu{}',# µ MICRO SIGN
 0x00b6: ur'\textparagraph{}', # ¶ PILCROW SIGN # != \textpilcrow
 0x00b9: ur'\textonesuperior{}',   # ¹ SUPERSCRIPT ONE
 0x00ba: ur'\textordmasculine{}',  # º MASCULINE ORDINAL INDICATOR
 0x00bc: ur'\textonequarter{}',# 1/4 FRACTION
 0x00bd: ur'\textonehalf{}',   # 1/2 FRACTION
 0x00be: ur'\textthreequarters{}', # 3/4 FRACTION
 0x00d7: ur'\texttimes{}', # × MULTIPLICATION SIGN
 0x00f7: ur'\textdiv{}',   # ÷ DIVISION SIGN
 # others
 0x0192: ur'\textflorin{}',# LATIN SMALL LETTER F WITH HOOK
 0x02b9: ur'\textasciiacute{}',# MODIFIER LETTER PRIME
 0x02ba: ur'\textacutedbl{}',  # MODIFIER LETTER DOUBLE PRIME
 0x2016: ur'\textbardbl{}',# DOUBLE VERTICAL LINE
 0x2022: ur'\textbullet{}',# BULLET
 0x2032: ur'\textasciiacute{}',# PRIME
 0x2033: ur'\textacutedbl{}',  # DOUBLE PRIME
 0x2035: ur'\textasciigrave{}',# REVERSED PRIME
 0x2036: ur'\textgravedbl{}',  # REVERSED DOUBLE PRIME
 0x203b: ur'\textreferencemark{}', # REFERENCE MARK
 0x203d: ur'\textinterrobang{}',   # INTERROBANG
 0x2044: ur'\textfractionsolidus{}', # FRACTION SLASH
 0x2045: ur'\textlquill{}',# LEFT SQUARE BRACKET WITH QUILL
 0x2046: ur'\textrquill{}',# RIGHT SQUARE BRACKET WITH QUILL
 0x2052: ur'\textdiscount{}',  # COMMERCIAL MINUS SIGN
 0x20a1: ur'\textcolonmonetary{}', # COLON SIGN
 0x20a3: ur'\textfrenchfranc{}',   # FRENCH FRANC SIGN
 0x20a4: ur'\textlira{}',  # LIRA SIGN
 0x20a6: ur'\textnaira{}', # NAIRA SIGN
 0x20a9: ur'\textwon{}',   # WON SIGN
 0x20ab: ur'\textdong{}',  # DONG SIGN
 0x20ac: ur'\texteuro{}',  # EURO SIGN
 0x20b1: ur'\textpeso{}',  # PESO SIGN
 0x20b2: ur'\textguarani{}',   # GUARANI SIGN
 

Re: New Feature Request: Chapter Contents

2013-10-06 Thread Andrew Parsloe

On 7/10/2013 4:49 a.m., Richard Heck wrote:

On 10/06/2013 07:33 AM, Mark Horton wrote:

Hi Developers

It would make navigation a lot easier for large documents if we had the
the ability to generate a contents of Chapters at the start.

Plus a more detailed contents page at the start of each Chapter.


This is a LaTeX issue, first and foremost. It's easy to get only the
chapters in the TOC initially. (See Document Settings Numbering and
TOC). It's getting the TOCs for each chapter that is the issue. But I
believe there are LaTeX packages that will do this. Go to CTAN.org and
search for them, or try googling. If you can find it, then, at a bare
minimum, you could do this with ERT, and you can also file an
enhancement request for native support for the package.

Richard



I've used the LaTeX minitoc package successfully with LyX for a large 
book (600 pages). It creates a table of contents for each chapter, 
inserted at the start of the chapter. I restricted the main TOC at the 
start of the book to section level, but each chapter TOC was to 
subsubsection level. Each chapter has \minitoc in ERT after the chapter 
heading, but that's all, so ERT use is minimal. The preamble to the 
master document (each chapter is a child document  has nothing in the 
preamble) has


\usepackage[tight]{minitoc}
\setcounter{minitocdepth}{3}
\setlength{\mtcindent}{24pt}
\renewcommand{\mtcfont}{\small\rm}
\renewcommand{\mtcSfont}{\small\bf}
\renewcommand{\mtcSSSfont}{\footnotesize\it}
\renewcommand{\mtctitle}{}

which shows the kind of tailoring to individual whims that is possible.

Andrew


Re: Cannot export Math manual using XeTeX

2013-10-06 Thread Scott Kostyshak
On Sun, Oct 6, 2013 at 11:57 AM, Guenter Milde mi...@users.sf.net wrote:
 On 2013-10-03, Scott Kostyshak wrote:
 On Thu, Oct 3, 2013 at 4:28 PM, Guenter Milde mi...@users.sf.net wrote:
 On 2013-10-03, Scott Kostyshak wrote:
 On Thu, Oct 3, 2013 at 5:02 AM, Guenter Milde mi...@users.sf.net wrote:
 On 2013-10-03, Scott Kostyshak wrote:
 Thanks for the confirmation. I started a thread on lyx-devel.
 Hopefully there's an easy way to have pdfTeX and XeTeX working. Note
 that if I remove the following lines from the preamble, export with
 XeTeX
 works fine (but pdfTeX is broken):

 \DeclareInputText{176}{\ifmmode^\circ\else\textdegree\fi}
 \DeclareInputText{183}{\ifmmode\cdot\else\textperiodcentered\fi}

 There is a simple fix: move the offending lines into the

 \ifpdf
 \fi

 block.

 However, the right way is to remove the lines as well as the section
 in the guide, because it is no longer true. Since several versions,
 LYXDIR/unicodesymbols contains the required definitions for text and
 math mode.

 I prefer the right way. So you suggest to remove the two
 DeclareInputText commands and to remove all of the section
 Miscellaneous special Characters ?

 After I do that, I get errors because of the € symbol. After I remove
 those occurrences, XeTeX and pdfTeX both export fine. There is an
 entry in unicodesymbols for the euro. Is this a different euro?

 The \texteuro macro is provided by the textcomp package.

 A quick and dirty fix would be to set the force flag so that the textcomp
 package is auto-loaded. However, this is an overkill as this would also
 replace the Euro (€) character with the \texteuro macro which is not
 required for the TeX input encodings
 utf8, ansinew, cp1250, cp1252, cp1257, cp858, latin10, and latin9

 A force-preamble flag that only forces loading the preamble code without
 forcing the replacement could solve the issue. For the textcomp feature
 this regards the characters
 # recognized with 'utf8', if textcomp is loaded
 textcomp = {
 # Latin-1 Supplement
 0x00a2: ur'\textcent{}',  # ¢ CENT SIGN
 0x00a4: ur'\textcurrency{}',  # ¤ CURRENCY SYMBOL
 0x00a5: ur'\textyen{}',   # ¥ YEN SIGN
 0x00a6: ur'\textbrokenbar{}', # ¦ BROKEN BAR
 0x00a7: ur'\textsection{}',   # § SECTION SIGN
 0x00a8: ur'\textasciidieresis{}', # ¨ DIAERESIS
 0x00a9: ur'\textcopyright{}', # © COPYRIGHT SIGN
 0x00aa: ur'\textordfeminine{}',   # ª FEMININE ORDINAL INDICATOR
 0x00ac: ur'\textlnot{}',  # ¬ NOT SIGN
 0x00ae: ur'\textregistered{}',# ® REGISTERED SIGN
 0x00af: ur'\textasciimacron{}',   # ¯ MACRON
 0x00b0: ur'\textdegree{}',# ° DEGREE SIGN
 0x00b1: ur'\textpm{}',# ± PLUS-MINUS SIGN
 0x00b2: ur'\texttwosuperior{}',   # ² SUPERSCRIPT TWO
 0x00b3: ur'\textthreesuperior{}', # ³ SUPERSCRIPT THREE
 0x00b4: ur'\textasciiacute{}',# ´ ACUTE ACCENT
 0x00b5: ur'\textmu{}',# µ MICRO SIGN
 0x00b6: ur'\textparagraph{}', # ¶ PILCROW SIGN # != \textpilcrow
 0x00b9: ur'\textonesuperior{}',   # ¹ SUPERSCRIPT ONE
 0x00ba: ur'\textordmasculine{}',  # º MASCULINE ORDINAL INDICATOR
 0x00bc: ur'\textonequarter{}',# 1/4 FRACTION
 0x00bd: ur'\textonehalf{}',   # 1/2 FRACTION
 0x00be: ur'\textthreequarters{}', # 3/4 FRACTION
 0x00d7: ur'\texttimes{}', # × MULTIPLICATION SIGN
 0x00f7: ur'\textdiv{}',   # ÷ DIVISION SIGN
 # others
 0x0192: ur'\textflorin{}',# LATIN SMALL LETTER F WITH HOOK
 0x02b9: ur'\textasciiacute{}',# MODIFIER LETTER PRIME
 0x02ba: ur'\textacutedbl{}',  # MODIFIER LETTER DOUBLE PRIME
 0x2016: ur'\textbardbl{}',# DOUBLE VERTICAL LINE
 0x2022: ur'\textbullet{}',# BULLET
 0x2032: ur'\textasciiacute{}',# PRIME
 0x2033: ur'\textacutedbl{}',  # DOUBLE PRIME
 0x2035: ur'\textasciigrave{}',# REVERSED PRIME
 0x2036: ur'\textgravedbl{}',  # REVERSED DOUBLE PRIME
 0x203b: ur'\textreferencemark{}', # REFERENCE MARK
 0x203d: ur'\textinterrobang{}',   # INTERROBANG
 0x2044: ur'\textfractionsolidus{}', # FRACTION SLASH
 0x2045: ur'\textlquill{}',# LEFT SQUARE BRACKET WITH QUILL
 0x2046: ur'\textrquill{}',# RIGHT SQUARE BRACKET WITH QUILL
 0x2052: ur'\textdiscount{}',  # COMMERCIAL MINUS SIGN
 0x20a1: ur'\textcolonmonetary{}', # COLON SIGN
 0x20a3: ur'\textfrenchfranc{}',   # FRENCH FRANC SIGN
 0x20a4: ur'\textlira{}',  # LIRA SIGN
 0x20a6: ur'\textnaira{}', # NAIRA SIGN
 0x20a9: ur'\textwon{}',   # WON SIGN
 0x20ab: ur'\textdong{}',  # DONG SIGN
 0x20ac: ur'\texteuro{}',  # EURO SIGN
 0x20b1: ur'\textpeso{}',   

Re: New Feature Request: Chapter Contents

2013-10-06 Thread Richard Heck

On 10/06/2013 07:33 AM, Mark Horton wrote:

 Hi Developers

 It would make navigation a lot easier for large documents if we had the
 the ability to generate a contents of Chapters at the start.

 Plus a more detailed contents page at the start of each Chapter.

This is a LaTeX issue, first and foremost. It's easy to get only the 
chapters in the TOC initially. (See Document Settings Numbering and 
TOC). It's getting the TOCs for each chapter that is the issue. But I 
believe there are LaTeX packages that will do this. Go to CTAN.org 
and search for them, or try googling. If you can find it, then, at a 
bare minimum, you could do this with ERT, and you can also file an 
enhancement request for native support for the package.




Thanks for the prompt reply.

I have found a package to do the job called Minitoc. Unfortunately 
being an ignorant beginner in this field  I don't know how to Install 
it  and make it work from Latex.


What OS are you using? There's probably a Package Manager of some sort 
you can use to install the package.


Andrew's instructions on how to use minitoc can be explained in more 
detail once we have the package installed.


Richard

PS Keep replies on the list, in case someone else has similar questions.



New Feature Request: Chapter Contents

2013-10-06 Thread Mark Horton
Hi Developers

It would make navigation a lot easier for large documents if we had the
the ability to generate a contents of Chapters at the start.

Plus a more detailed contents page at the start of each Chapter. 


Best Regards

Mark Horton



Re: New Feature Request: Chapter Contents

2013-10-06 Thread Richard Heck

On 10/06/2013 07:33 AM, Mark Horton wrote:

Hi Developers

It would make navigation a lot easier for large documents if we had the
the ability to generate a contents of Chapters at the start.

Plus a more detailed contents page at the start of each Chapter.


This is a LaTeX issue, first and foremost. It's easy to get only the 
chapters in the TOC initially. (See Document> Settings> Numbering and 
TOC). It's getting the TOCs for each chapter that is the issue. But I 
believe there are LaTeX packages that will do this. Go to CTAN.org and 
search for them, or try googling. If you can find it, then, at a bare 
minimum, you could do this with ERT, and you can also file an 
enhancement request for native support for the package.


Richard



Re: Cannot export Math manual using XeTeX

2013-10-06 Thread Guenter Milde
On 2013-10-03, Scott Kostyshak wrote:
> On Thu, Oct 3, 2013 at 4:28 PM, Guenter Milde  wrote:
>> On 2013-10-03, Scott Kostyshak wrote:
>>> On Thu, Oct 3, 2013 at 5:02 AM, Guenter Milde  wrote:
 On 2013-10-03, Scott Kostyshak wrote:
> Thanks for the confirmation. I started a thread on lyx-devel.
> Hopefully there's an easy way to have pdfTeX and XeTeX working. Note
> that if I remove the following lines from the preamble, export with
> XeTeX
> works fine (but pdfTeX is broken):

> \DeclareInputText{176}{\ifmmode^\circ\else\textdegree\fi}
> \DeclareInputText{183}{\ifmmode\cdot\else\textperiodcentered\fi}

 There is a simple fix: move the offending lines into the

 \ifpdf
 \fi

 block.

 However, the right way is to remove the lines as well as the section
 in the guide, because it is no longer true. Since several versions,
 LYXDIR/unicodesymbols contains the required definitions for text and
 math mode.

>>> I prefer the right way. So you suggest to remove the two
>>> DeclareInputText commands and to remove all of the section
>>> "Miscellaneous special Characters" ?

>>> After I do that, I get errors because of the € symbol. After I remove
>>> those occurrences, XeTeX and pdfTeX both export fine. There is an
>>> entry in unicodesymbols for the euro. Is this a different euro?

>> The \texteuro macro is provided by the "textcomp" package.

>> A quick and dirty fix would be to set the "force" flag so that the textcomp
>> package is auto-loaded. However, this is an overkill as this would also
>> replace the Euro (€) character with the \texteuro macro which is not
>> required for the TeX input encodings
>> utf8, ansinew, cp1250, cp1252, cp1257, cp858, latin10, and latin9

>> A "force-preamble" flag that only forces loading the preamble code without
>> forcing the replacement could solve the issue. For the "textcomp" feature
>> this regards the characters
>> # recognized with 'utf8', if textcomp is loaded
>> textcomp = {
>> # Latin-1 Supplement
>> 0x00a2: ur'\textcent{}',  # ¢ CENT SIGN
>> 0x00a4: ur'\textcurrency{}',  # ¤ CURRENCY SYMBOL
>> 0x00a5: ur'\textyen{}',   # ¥ YEN SIGN
>> 0x00a6: ur'\textbrokenbar{}', # ¦ BROKEN BAR
>> 0x00a7: ur'\textsection{}',   # § SECTION SIGN
>> 0x00a8: ur'\textasciidieresis{}', # ¨ DIAERESIS
>> 0x00a9: ur'\textcopyright{}', # © COPYRIGHT SIGN
>> 0x00aa: ur'\textordfeminine{}',   # ª FEMININE ORDINAL INDICATOR
>> 0x00ac: ur'\textlnot{}',  # ¬ NOT SIGN
>> 0x00ae: ur'\textregistered{}',# ® REGISTERED SIGN
>> 0x00af: ur'\textasciimacron{}',   # ¯ MACRON
>> 0x00b0: ur'\textdegree{}',# ° DEGREE SIGN
>> 0x00b1: ur'\textpm{}',# ± PLUS-MINUS SIGN
>> 0x00b2: ur'\texttwosuperior{}',   # ² SUPERSCRIPT TWO
>> 0x00b3: ur'\textthreesuperior{}', # ³ SUPERSCRIPT THREE
>> 0x00b4: ur'\textasciiacute{}',# ´ ACUTE ACCENT
>> 0x00b5: ur'\textmu{}',# µ MICRO SIGN
>> 0x00b6: ur'\textparagraph{}', # ¶ PILCROW SIGN # != \textpilcrow
>> 0x00b9: ur'\textonesuperior{}',   # ¹ SUPERSCRIPT ONE
>> 0x00ba: ur'\textordmasculine{}',  # º MASCULINE ORDINAL INDICATOR
>> 0x00bc: ur'\textonequarter{}',# 1/4 FRACTION
>> 0x00bd: ur'\textonehalf{}',   # 1/2 FRACTION
>> 0x00be: ur'\textthreequarters{}', # 3/4 FRACTION
>> 0x00d7: ur'\texttimes{}', # × MULTIPLICATION SIGN
>> 0x00f7: ur'\textdiv{}',   # ÷ DIVISION SIGN
>> # others
>> 0x0192: ur'\textflorin{}',# LATIN SMALL LETTER F WITH HOOK
>> 0x02b9: ur'\textasciiacute{}',# MODIFIER LETTER PRIME
>> 0x02ba: ur'\textacutedbl{}',  # MODIFIER LETTER DOUBLE PRIME
>> 0x2016: ur'\textbardbl{}',# DOUBLE VERTICAL LINE
>> 0x2022: ur'\textbullet{}',# BULLET
>> 0x2032: ur'\textasciiacute{}',# PRIME
>> 0x2033: ur'\textacutedbl{}',  # DOUBLE PRIME
>> 0x2035: ur'\textasciigrave{}',# REVERSED PRIME
>> 0x2036: ur'\textgravedbl{}',  # REVERSED DOUBLE PRIME
>> 0x203b: ur'\textreferencemark{}', # REFERENCE MARK
>> 0x203d: ur'\textinterrobang{}',   # INTERROBANG
>> 0x2044: ur'\textfractionsolidus{}', # FRACTION SLASH
>> 0x2045: ur'\textlquill{}',# LEFT SQUARE BRACKET WITH QUILL
>> 0x2046: ur'\textrquill{}',# RIGHT SQUARE BRACKET WITH QUILL
>> 0x2052: ur'\textdiscount{}',  # COMMERCIAL MINUS SIGN
>> 0x20a1: ur'\textcolonmonetary{}', # COLON SIGN
>> 0x20a3: ur'\textfrenchfranc{}',   # FRENCH FRANC SIGN
>> 0x20a4: ur'\textlira{}',  # LIRA SIGN
>> 0x20a6: ur'\textnaira{}', # NAIRA SIGN
>> 0x20a9: ur'\textwon{}',   # WON 

Re: New Feature Request: Chapter Contents

2013-10-06 Thread Andrew Parsloe

On 7/10/2013 4:49 a.m., Richard Heck wrote:

On 10/06/2013 07:33 AM, Mark Horton wrote:

Hi Developers

It would make navigation a lot easier for large documents if we had the
the ability to generate a contents of Chapters at the start.

Plus a more detailed contents page at the start of each Chapter.


This is a LaTeX issue, first and foremost. It's easy to get only the
chapters in the TOC initially. (See Document> Settings> Numbering and
TOC). It's getting the TOCs for each chapter that is the issue. But I
believe there are LaTeX packages that will do this. Go to CTAN.org and
search for them, or try googling. If you can find it, then, at a bare
minimum, you could do this with ERT, and you can also file an
enhancement request for native support for the package.

Richard



I've used the LaTeX minitoc package successfully with LyX for a large 
book (600 pages). It creates a table of contents for each chapter, 
inserted at the start of the chapter. I restricted the main TOC at the 
start of the book to section level, but each chapter TOC was to 
subsubsection level. Each chapter has \minitoc in ERT after the chapter 
heading, but that's all, so ERT use is minimal. The preamble to the 
master document (each chapter is a child document & has nothing in the 
preamble) has


\usepackage[tight]{minitoc}
\setcounter{minitocdepth}{3}
\setlength{\mtcindent}{24pt}
\renewcommand{\mtcfont}{\small\rm}
\renewcommand{\mtcSfont}{\small\bf}
\renewcommand{\mtcSSSfont}{\footnotesize\it}
\renewcommand{\mtctitle}{}

which shows the kind of tailoring to individual whims that is possible.

Andrew


Re: Cannot export Math manual using XeTeX

2013-10-06 Thread Scott Kostyshak
On Sun, Oct 6, 2013 at 11:57 AM, Guenter Milde  wrote:
> On 2013-10-03, Scott Kostyshak wrote:
>> On Thu, Oct 3, 2013 at 4:28 PM, Guenter Milde  wrote:
>>> On 2013-10-03, Scott Kostyshak wrote:
 On Thu, Oct 3, 2013 at 5:02 AM, Guenter Milde  wrote:
> On 2013-10-03, Scott Kostyshak wrote:
>> Thanks for the confirmation. I started a thread on lyx-devel.
>> Hopefully there's an easy way to have pdfTeX and XeTeX working. Note
>> that if I remove the following lines from the preamble, export with
>> XeTeX
>> works fine (but pdfTeX is broken):
>
>> \DeclareInputText{176}{\ifmmode^\circ\else\textdegree\fi}
>> \DeclareInputText{183}{\ifmmode\cdot\else\textperiodcentered\fi}
>
> There is a simple fix: move the offending lines into the
>
> \ifpdf
> \fi
>
> block.
>
> However, the right way is to remove the lines as well as the section
> in the guide, because it is no longer true. Since several versions,
> LYXDIR/unicodesymbols contains the required definitions for text and
> math mode.
>
 I prefer the right way. So you suggest to remove the two
 DeclareInputText commands and to remove all of the section
 "Miscellaneous special Characters" ?
>
 After I do that, I get errors because of the € symbol. After I remove
 those occurrences, XeTeX and pdfTeX both export fine. There is an
 entry in unicodesymbols for the euro. Is this a different euro?
>
>>> The \texteuro macro is provided by the "textcomp" package.
>
>>> A quick and dirty fix would be to set the "force" flag so that the textcomp
>>> package is auto-loaded. However, this is an overkill as this would also
>>> replace the Euro (€) character with the \texteuro macro which is not
>>> required for the TeX input encodings
>>> utf8, ansinew, cp1250, cp1252, cp1257, cp858, latin10, and latin9
>
>>> A "force-preamble" flag that only forces loading the preamble code without
>>> forcing the replacement could solve the issue. For the "textcomp" feature
>>> this regards the characters
>>> # recognized with 'utf8', if textcomp is loaded
>>> textcomp = {
>>> # Latin-1 Supplement
>>> 0x00a2: ur'\textcent{}',  # ¢ CENT SIGN
>>> 0x00a4: ur'\textcurrency{}',  # ¤ CURRENCY SYMBOL
>>> 0x00a5: ur'\textyen{}',   # ¥ YEN SIGN
>>> 0x00a6: ur'\textbrokenbar{}', # ¦ BROKEN BAR
>>> 0x00a7: ur'\textsection{}',   # § SECTION SIGN
>>> 0x00a8: ur'\textasciidieresis{}', # ¨ DIAERESIS
>>> 0x00a9: ur'\textcopyright{}', # © COPYRIGHT SIGN
>>> 0x00aa: ur'\textordfeminine{}',   # ª FEMININE ORDINAL INDICATOR
>>> 0x00ac: ur'\textlnot{}',  # ¬ NOT SIGN
>>> 0x00ae: ur'\textregistered{}',# ® REGISTERED SIGN
>>> 0x00af: ur'\textasciimacron{}',   # ¯ MACRON
>>> 0x00b0: ur'\textdegree{}',# ° DEGREE SIGN
>>> 0x00b1: ur'\textpm{}',# ± PLUS-MINUS SIGN
>>> 0x00b2: ur'\texttwosuperior{}',   # ² SUPERSCRIPT TWO
>>> 0x00b3: ur'\textthreesuperior{}', # ³ SUPERSCRIPT THREE
>>> 0x00b4: ur'\textasciiacute{}',# ´ ACUTE ACCENT
>>> 0x00b5: ur'\textmu{}',# µ MICRO SIGN
>>> 0x00b6: ur'\textparagraph{}', # ¶ PILCROW SIGN # != \textpilcrow
>>> 0x00b9: ur'\textonesuperior{}',   # ¹ SUPERSCRIPT ONE
>>> 0x00ba: ur'\textordmasculine{}',  # º MASCULINE ORDINAL INDICATOR
>>> 0x00bc: ur'\textonequarter{}',# 1/4 FRACTION
>>> 0x00bd: ur'\textonehalf{}',   # 1/2 FRACTION
>>> 0x00be: ur'\textthreequarters{}', # 3/4 FRACTION
>>> 0x00d7: ur'\texttimes{}', # × MULTIPLICATION SIGN
>>> 0x00f7: ur'\textdiv{}',   # ÷ DIVISION SIGN
>>> # others
>>> 0x0192: ur'\textflorin{}',# LATIN SMALL LETTER F WITH HOOK
>>> 0x02b9: ur'\textasciiacute{}',# MODIFIER LETTER PRIME
>>> 0x02ba: ur'\textacutedbl{}',  # MODIFIER LETTER DOUBLE PRIME
>>> 0x2016: ur'\textbardbl{}',# DOUBLE VERTICAL LINE
>>> 0x2022: ur'\textbullet{}',# BULLET
>>> 0x2032: ur'\textasciiacute{}',# PRIME
>>> 0x2033: ur'\textacutedbl{}',  # DOUBLE PRIME
>>> 0x2035: ur'\textasciigrave{}',# REVERSED PRIME
>>> 0x2036: ur'\textgravedbl{}',  # REVERSED DOUBLE PRIME
>>> 0x203b: ur'\textreferencemark{}', # REFERENCE MARK
>>> 0x203d: ur'\textinterrobang{}',   # INTERROBANG
>>> 0x2044: ur'\textfractionsolidus{}', # FRACTION SLASH
>>> 0x2045: ur'\textlquill{}',# LEFT SQUARE BRACKET WITH QUILL
>>> 0x2046: ur'\textrquill{}',# RIGHT SQUARE BRACKET WITH QUILL
>>> 0x2052: ur'\textdiscount{}',  # COMMERCIAL MINUS SIGN
>>> 0x20a1: ur'\textcolonmonetary{}', # COLON SIGN
>>> 0x20a3: ur'\textfrenchfranc{}',   # FRENCH FRANC SIGN

Re: New Feature Request: Chapter Contents

2013-10-06 Thread Richard Heck

On 10/06/2013 07:33 AM, Mark Horton wrote:

> Hi Developers
>
> It would make navigation a lot easier for large documents if we had the
> the ability to generate a contents of Chapters at the start.
>
> Plus a more detailed contents page at the start of each Chapter.

This is a LaTeX issue, first and foremost. It's easy to get only the 
chapters in the TOC initially. (See Document> Settings> Numbering and 
TOC). It's getting the TOCs for each chapter that is the issue. But I 
believe there are LaTeX packages that will do this. Go to CTAN.org 
and search for them, or try googling. If you can find it, then, at a 
bare minimum, you could do this with ERT, and you can also file an 
enhancement request for native support for the package.




Thanks for the prompt reply.

I have found a "package" to do the job called Minitoc. Unfortunately 
being an ignorant beginner in this field  I don't know how to "Install 
it " and make it work from Latex.


What OS are you using? There's probably a Package Manager of some sort 
you can use to install the package.


Andrew's instructions on how to use minitoc can be explained in more 
detail once we have the package installed.


Richard

PS Keep replies on the list, in case someone else has similar questions.