diff options
Diffstat (limited to 'support/bib2gls/src/bib2gls-terms.bib')
-rw-r--r-- | support/bib2gls/src/bib2gls-terms.bib | 101 |
1 files changed, 87 insertions, 14 deletions
diff --git a/support/bib2gls/src/bib2gls-terms.bib b/support/bib2gls/src/bib2gls-terms.bib index 8ca871f605..27841562da 100644 --- a/support/bib2gls/src/bib2gls-terms.bib +++ b/support/bib2gls/src/bib2gls-terms.bib @@ -1,22 +1,35 @@ % Encoding: UTF-8 +@entry{entrytype, + name={entry type}, + description={an entry's identifying type, as specified by \atentryfmt{entry-type}. + (Not to be confused with the glossary label, which is identified by + the \field{type} field.) When referenced in a resource option, the + leading \code{@} is typically omitted. The \emph{original} entry type + refers to the entry type as specified in the \ext{bib} file. The + \emph{actual} entry type may be different and will be the result + of a conversion via resource options such as \csopt{entry-type-aliases}. + Although the \ext{bib} format is case-insensitive, references to the + entry type in resource options should typically be in \idx{lowercase}.} +} + @entry{primaryentry, name={primary entry}, plural={primary entries}, - user1`={idx.primary}, - description={The original entry created from a dual-entry type - (such as \atentry{dualentry}) or the entry from single-entry - types (such as \atentry{entry}) or \glspl{spawnedentry}.} + user1={idx.primary}, + description={The original entry created from a dual-\gls{entrytype} + (such as \atentry{dualentry}) or the entry from + single-\glspl{entrytype} (such as \atentry{entry}) or \glspl{spawnedentry}.} } @entry{dualentry, name={dual entry}, plural={dual entries}, user1={idx.dual}, - description={The duplicate entry created from a dual-entry type + description={The duplicate entry created from a dual-\gls{entrytype} (such as \atentry{dualentry}). This duplicate is based on the \gls{primaryentry} with modifications made according to various - settings. With tertiary entry types, the dual entry represents + settings. With tertiary \glspl{entrytype}, the dual entry represents two entries: the \glsdisp{secondaryentry}{secondary} and \glsdisp{tertiaryentry}{tertiary}. See \sectionref{sec:dualentry}.} @@ -26,7 +39,7 @@ name={secondary entry}, plural={secondary entries}, user1={idx.secondary}, - description={For the tertiary entry types, such as + description={For the tertiary \glspl{entrytype}, such as \atentry{tertiaryindexabbreviationentry}, there are only actually two objects defined within \bibgls: the \glsdisp{primaryentry}{primary} and the \glsdisp{dualentry}{dual}, @@ -43,8 +56,8 @@ user1={idx.tertiary}, description={An entry that isn't defined as a separated object within \bibgls, but is defined within the \ext{glstex} file - as a by-product of the dual definition code for tertiary entry - types.} + as a by-product of the dual definition code for tertiary + \glspl{entrytype}.} } @entry{mainentry, @@ -52,7 +65,7 @@ plural={main entries}, description={The originating entry from which the \glspl{spawnedentry} are created. A main entry may - be a dual-entry type, consisting of a \gls{primaryentry} + be a dual-\gls{entrytype}, consisting of a \gls{primaryentry} and \gls{dualentry}. (Not to be confused with the main glossary or the \gls{compmainlabel} of a \gls{compoundentry}.)} @@ -62,20 +75,20 @@ name={progenitor}, user1={idx.progenitor}, description={The \gls{mainentry} for the \atentry{progenitor} - entry type.} + \gls{entrytype}.} } @entry{progeny, name={progeny}, user1={idx.progeny}, description={The \glspl{spawnedentry} for the \atentry{progenitor} - entry type.} + \gls{entrytype}.} } @entry{multientrytype, name={multi-entry type}, - description={An entry type that can spawn multiple - \glspl{primaryentry}. Some multi-entry types can also spawn a + description={An \gls{entrytype} that can spawn multiple + \glspl{primaryentry}. Some multi-\glspl{entrytype} can also spawn a \gls{dualentry}. See \sectionref{sec:multientry}. For the \sty{glossaries-extra} \qt{multi (compound or combined) entries} that are defined with \cs{multiglossaryentry} see \gls{compoundentry}.} @@ -310,6 +323,7 @@ plural={top-level entries}, user1={idx.hierarchical-entry}, description={An entry that doesn't have a \gls{parententry}. + This entry is the hierarchical root for all its descendents. See \sectionref{sec:hierarchicalopts}.} } @@ -387,6 +401,36 @@ description={\gls{glsxtrresourcefile} or \gls{GlsXtrLoadResources}.} } +@entry{resource-locale, + name = {resource locale}, + user1={idx.locale-resource}, + description={the default locale for the given \gls{resourceset}. + This can be set with the \csopt{locale} resource option. If not + explicitly set, then the default will be the document language, if + it has been detected by \sty{tracklang} or identified with + \longarg{locale}, or the \idx{JRE} locale otherwise.} +} + +@entry{document-locale, + name = {document locale}, + user1={idx.locale-doc}, + description={the locale associated with the document + language (or by \longarg{locale}, if no document language has been + detected). In the case of a multi-lingual document, this + is the locale of the last language resource file to be loaded through + \isty{tracklang}'s interface. It's best to explicitly set the locale + for multi-lingual documents to avoid confusion (either with + the \csopt{locale} or as a language tag in options such as + \csopt{sort}).} +} + +@entry{Java-locale, + name = {Java locale}, + user1={idx.locale-Java}, + description={the default locale for the \idx{JRE}, which usually + matches the operating system's locale.} +} + @entry{crossresourceref, name={cross-resource reference}, user1={idx.crossresourceref}, @@ -460,3 +504,32 @@ Files, Text Files and File Encodings} for further information about description = {The non-\glslink{compmainlabel}{main} elements in the set that defines a \gls{compoundentry}.} } + +@entry{regular-expression, + name = {regular expression}, + user1={idx.regex}, + description={A pattern that specifies how to match text. Unless + indicated otherwise, resource options that use regular expressions + are \gls{anchored}. See + \href{http://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html}{Java's + Pattern class API}~\cite{pattern} for details of the regular + expression syntax.} +} + +@entry{anchored, + name = {anchored (regular expression)}, + text={anchored}, + description={An anchored \gls{regular-expression} must match the entire + string, not a sub-string. For example, \code{l\idx{zeroorone}op} matches \qt{lop} + and \qt{op} but doesn't match \qt{clop} or \qt{cop}.} +} + +@entry{concatenation, + name={concatenation}, + user1={idx.stringconcatenation}, + description={This is where multiple fragments or substrings are + joined together to form a single value. The concatenation operator + is \idx{stringconcat} for \ext{bib} files (see + \sectionref{sec:bibstringconcat}) and \idx{concat-plus} for + resource option string concatenation (\sectionref{sec:optstringconcat}).} +} |