anne/lyx_mirror
1
0
Fork 0
mirror of https://git.lyx.org/repos/lyx.git synced 2024-11-25 10:58:52 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
309f863d0e
lyx_mirror/lib/layouts/foottoend.module

36 lines
959 B
Plaintext
Raw Normal View History

Add support for the enotez package This is a modern implementation of endnotes building on LaTeX3 tools which gets away with deficiencies of the endnotes package, has some extra features, is localized, supports hyperref and is better customizable. As this is a fairly new package requiring l3, we keep the old endnotes module and provide this as an alternative.
2019-08-13 05:30:20 +00:00
#\DeclareLyXModule[endnotes.sty]{Footnotes as Endnotes (Basic)}
Make module categories (almost) great again The category tag was rarely used and thus not very useful. This adds categorization to most modules (the rest will follow) and uses the \DeclareCategory tag we use in layouts rather than the extra syntax we used in modules. Categories are now added to the po files and translated. Note that this is work in progress: the current categories are still subject to change. The ultimate goal of this is to sort the modules in the GUI by category as we do with layouts, examples and templates (and add a filter to search for specific modules) As it is now (with the many modules we accumulated), the module selector is not really usable anymore. If you don't happen to know how exactly a module is named, selecting a module is really a PITA.
2019-04-04 16:43:29 +00:00
#\DeclareCategory{Foot- and Endnotes}
This commit adds some new functionality to the modules stuff. In particular, it introduces the concept of "required" and "excluded" modules: A given module may require one of some list of modules, or it may be incompatible with some other modules. (Complex Boolean combinations are not supported!!) These facts can be noted in the module file, and the UI responds appropriately: Required and excluded modules are noted in the description, and the "Add" button is enabled only if at least one of the required modules has already been selected and no excluded module is selected. Getting this to work involved a fair bit of cleanup of the existing code---including ways Angus, I think, had already pointed out were required---and also involved changing the syntax of the headers of the module files, but in ways that are probably best anyway. None of the extant modules require any other modules, but the Theorem modules all exclude one another. (See the screenshot.) When I modularize the AMS classes---that is the next task---we'll have requires. git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@22456 a592a061-630c-0410-9148-cb99ea01b6c8
2008-01-09 18:51:02 +00:00
#DescriptionBegin
Add support for the enotez package This is a modern implementation of endnotes building on LaTeX3 tools which gets away with deficiencies of the endnotes package, has some extra features, is localized, supports hyperref and is better customizable. As this is a fairly new package requiring l3, we keep the old endnotes module and provide this as an alternative.
2019-08-13 05:30:20 +00:00
#Sets all footnotes as endnotes. This uses the endnotes
#package, which has some limitations but works with older LaTeX distributions
#as well. You will need to add an endnotes list
#(Insert > List/Contents/References > Endnotes) where you
Extend endnotes support Support native solution for Endnotes list rather than having to use \\theendnotes via ERT File format change
2019-08-12 11:00:54 +00:00
#want the endnotes to appear.
This commit adds some new functionality to the modules stuff. In particular, it introduces the concept of "required" and "excluded" modules: A given module may require one of some list of modules, or it may be incompatible with some other modules. (Complex Boolean combinations are not supported!!) These facts can be noted in the module file, and the UI responds appropriately: Required and excluded modules are noted in the description, and the "Add" button is enabled only if at least one of the required modules has already been selected and no excluded module is selected. Getting this to work involved a fair bit of cleanup of the existing code---including ways Angus, I think, had already pointed out were required---and also involved changing the syntax of the headers of the module files, but in ways that are probably best anyway. None of the extant modules require any other modules, but the Theorem modules all exclude one another. (See the screenshot.) When I modularize the AMS classes---that is the next task---we'll have requires. git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@22456 a592a061-630c-0410-9148-cb99ea01b6c8
2008-01-09 18:51:02 +00:00
#DescriptionEnd
Add support for the enotez package This is a modern implementation of endnotes building on LaTeX3 tools which gets away with deficiencies of the endnotes package, has some extra features, is localized, supports hyperref and is better customizable. As this is a fairly new package requiring l3, we keep the old endnotes module and provide this as an alternative.
2019-08-13 05:30:20 +00:00
#Excludes: enotez | foottoenotez
This is one of a series of patches that will merge the layout modules development in personal/branches/rgheck back into the tree. Design goal: Allow the use of layout "modules", which are to LaTeX packages as layout files are to LaTeX document classes. Thus, one could have a module that defined certain character styles, environments, commands, or what have you, and include it in various documents, each of which uses a different document class, without having to modify the layout files themselves. For example, a theorems.module could be used with article.layout to provide support for theorem-type environments, without having to modify article.layout itself, and the same module could be used with book.layout, etc. This patch adds the backend. The ModuleList class holds a list of the available modules, which are retrieved from lyxmodules.lst, itself generated by configure.py. There are two LFUNs available: modules-clear and module-add, which do the obvious thing; you can test by typing these into the minibuffer, along with the name of one of the available modules: URL (a CharStyle), Endnote (a Custom Inset), and---with the spaces---End To Foot (View>LaTeX and look at the user preamble), which are themselves in lib/layouts. There are some others, too, that allow theorems to be added to classes like article and book. The GUI will come next. Issues: (i) The configure.py script could be improved. It'd be nice, for example, if it tested for the presence of the LaTeX packages a particular module needs. But this would mean re-working the LaTeX script, and I don't know how to do that. Note that at present, the packages are ignored. This will change shortly. (ii) I've used std::string in LyXModule, following what seemed to be a precedent in TextClass. If some of these should be docstrings, please let me know, and I'll change them. (iii) There is at present no distinction between LaTeX and DocBook modules. Should there be? That is: Should there be modules that are available when the document class is a LaTeX class and others that are available only when it is DocBook? Or should there just be one set of modules? Each module can of course indicate for what it is suitable in its description. git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@19893 a592a061-630c-0410-9148-cb99ea01b6c8
2007-08-29 17:59:49 +00:00
Update layouts to format 98
2022-12-06 06:02:22 +00:00
Format 98
*** Requires tag for classes, layouts and custom insets *** * src/TextClass{cpp,h}: - implement Requires tag for class and InsetLayout. * src/Layout.{cpp,h}: - implement Requires tag for layouts. - increase layouts format to 6. * src/Paragraph.cpp: - request required features for paragraph layouts. * src/LaTeXFeatures.cpp: - add some packages needed by modules. - remove Preamble method for InsetLayout. This is now done in InsetFlex::validate. * src/BufferParams.cpp (validate): - request required features for the class. * src/insets/InsetLayout.h: - new member "requires". * src/insets/InsetFlex.{cpp,h}: - implement validate method and request required features and preamble snippets. * lib/layouts/*.{layout,module,inc}: - increase layouts format to 6. - use Requires tags in some modules (more can be done later). * lib/doc/Customization.lyx: - document Requires tag. git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@22414 a592a061-630c-0410-9148-cb99ea01b6c8
2008-01-07 16:59:10 +00:00
This is one of a series of patches that will merge the layout modules development in personal/branches/rgheck back into the tree. Design goal: Allow the use of layout "modules", which are to LaTeX packages as layout files are to LaTeX document classes. Thus, one could have a module that defined certain character styles, environments, commands, or what have you, and include it in various documents, each of which uses a different document class, without having to modify the layout files themselves. For example, a theorems.module could be used with article.layout to provide support for theorem-type environments, without having to modify article.layout itself, and the same module could be used with book.layout, etc. This patch adds the backend. The ModuleList class holds a list of the available modules, which are retrieved from lyxmodules.lst, itself generated by configure.py. There are two LFUNs available: modules-clear and module-add, which do the obvious thing; you can test by typing these into the minibuffer, along with the name of one of the available modules: URL (a CharStyle), Endnote (a Custom Inset), and---with the spaces---End To Foot (View>LaTeX and look at the user preamble), which are themselves in lib/layouts. There are some others, too, that allow theorems to be added to classes like article and book. The GUI will come next. Issues: (i) The configure.py script could be improved. It'd be nice, for example, if it tested for the presence of the LaTeX packages a particular module needs. But this would mean re-working the LaTeX script, and I don't know how to do that. Note that at present, the packages are ignored. This will change shortly. (ii) I've used std::string in LyXModule, following what seemed to be a precedent in TextClass. If some of these should be docstrings, please let me know, and I'll change them. (iii) There is at present no distinction between LaTeX and DocBook modules. Should there be? That is: Should there be modules that are available when the document class is a LaTeX class and others that are available only when it is DocBook? Or should there just be one set of modules? Each module can of course indicate for what it is suitable in its description. git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@19893 a592a061-630c-0410-9148-cb99ea01b6c8
2007-08-29 17:59:49 +00:00
foottoend.module: no need to tinker with redefinitions when we just can output what we want right away.
2019-08-12 12:48:21 +00:00
InsetLayout Foot
Localize endnotes header (with endnotes.sty)
2019-08-13 08:13:32 +00:00
LabelString Endnote
LatexName endnote
Requires endnotes
LangPreamble
typo
2020-07-30 14:25:03 +00:00
\providecommand{\notesname}{_(Notes[[Endnotes]])}
Localize endnotes header (with endnotes.sty)
2019-08-13 08:13:32 +00:00
EndLangPreamble
BabelPreamble
typo
2020-07-30 14:25:03 +00:00
\addto\captions$$lang{\renewcommand{\notesname}{_(Notes[[Endnotes]])}}
Localize endnotes header (with endnotes.sty)
2019-08-13 08:13:32 +00:00
EndBabelPreamble
foottoend.module: no need to tinker with redefinitions when we just can output what we want right away.
2019-08-12 12:48:21 +00:00
End
Extend endnotes support Support native solution for Endnotes list rather than having to use \\theendnotes via ERT File format change
2019-08-12 11:00:54 +00:00
# We are only interested in the list
Float
Type endnote
ListName "Endnotes"
IsPredefined true
UsesFloatPkg false
ListCommand theendnotes
Requires endnotes
End
Reference in New Issue Copy Permalink