# Encoding: UTF-8 # English language file for makeglossaries-gui # Tab -> \t newline -> \n literal backslash -> \\ # Control sequence (literal) -> |csname| # File menu file=File file.mnemonic=F file.open=Open... file.open.mnemonic=O file.open.tooltip=Load an auxiliary (.aux) file file.open.alttext=Load File file.reload=Reload file.reload.mnemonic=R file.reload.tooltip=Reload current file file.reload.alttext=Reload file.recent=Recent file.recent.mnemonic=T file.quit=Quit file.quit.mnemonic=Q # Settings menu settings=Settings settings.mnemonic=S settings.incsize=Increase Font Size settings.incsize.mnemonic=I settings.incsize.tooltip=Increase font size settings.incsize.alttext=Increase Font Size settings.decsize=Decrease Font Size settings.decsize.mnemonic=D settings.decsize.tooltip=Decrease font size settings.decsize.alttext=Decrease Font Size settings.dryrun=Dry Run Mode settings.dryrun.mnemonic=N settings.editproperties=Edit Properties... settings.editproperties.mnemonic=P settings.editproperties.tooltip=Edit application settings settings.editproperties.alttext=Settings # Help menu help=Help help.mnemonic=H help.about=About help.about.mnemonic=A help.license=License help.license.mnemonic=L help.manual=Manual help.manual.mnemonic=M help.manual.tooltip=Manual help.manual.alttext=Help # about dialog about.title=About {0} about.version=Version {0} ({1}) about.copyright=Copyright {0} {1} about.translator_info= # StdOut Syntax syntax.cmdline=makeglossariesgui [] [] syntax.filename= is required with the {0} option. The ".aux" extension may be omitted. syntax.options=Options: syntax.batch={0} (or {1})\t\trun in batch mode syntax.gui={0}\t\t\trun in GUI mode (default) syntax.quiet={0}\t\t\tsuppress messages normally written to stdout syntax.help={0} (or {1})\t\tprint the help message syntax.version={0} (or {1})\tprint the application version syntax.debug={0}\t\t\tprint debug messages to stdout syntax.dryrun={0} (or {1})\tdry run mode syntax.nodryrun={0}\t\tnot dry run mode (default) # file filter filter.aux=Auxiliary (AUX) Files # application selector appselect.title=Select Application appselect.pathlabel=Select path to application appselect.pathlabel.mnemonic=P app.title={0} - {1} # Main panel main.title=General Information main.title.mnemonic=I main.aux=Main AUX File: main.order=Order: main.ist=Style File: main.list=Defined Glossaries: main.indexer=Index Format: main.encoding=Indexer Encoding: main.docencoding=Document Encoding: main.glossary=Glossary {0}: main.glossary.log=Transcript: main.glossary.gls=Output: main.glossary.glo=Input: main.glossary.language=Language: main.glossary.codepage=Code Page: main.up_to_date=Up to date main.out_of_date=Out of date main.empty=Empty main.num_entries=Number of Entries: main.view=View main.details=Details # Entry viewer entry.title=Glossary ''{0}'' entry.label=Entry Tag entry.sort=Sort entry.count=Occurrences entry.find=Find entry.find.tooltip=Find entry entry.find_label=Tag: entry.find_label.mnemonic=T # popup menu popup.select_all=Select All popup.select_all.mnemonic=A popup.copy=Copy popup.copy.mnemonic=C # Diagnostics panel diagnostics.title=Diagnostics diagnostics.title.mnemonic=D diagnostics.no_file=Use {0} > {1} to parse your document''s .aux file. diagnostics.advisory=Advisory Notes: diagnostics.no_glossaries=Either your document hasn''t loaded the glossaries package, or you have selected the wrong auxiliary file. diagnostics.no_version=Can''t detect the version number for the glossaries package. Have you remembered to load it (|usepackage|'{'glossaries'}')? diagnostics.not_aux=The file you have selected doesn''t seem to be an auxiliary (.aux) file. diagnostics.no_makeglossaries=Your document doesn''t seem to have used |makeglossaries| or the appropriate information hasn''t been correctly written to the .aux file. diagnostics.no_errors=No errors detected. If you are missing entries, check the following:

Have you used commands like |gls| or |glsadd| in the document?
If you have used commands like |glsadd| or |glsaddall| in the preamble, have you remembered to put them after |makeglossaries|?
If you have cross-referenced entries (for example, you have only referenced an entry in the description of another entry) you may need to retry making the glossaries after you have rerun LaTeX. (If you have used the see key, you might want to consider using glossaries-extra if you haven''t already done so.)
If you have at least version 4.24 of the glossaries package, have you used the debug option? (That might provide some more information for me to analyse.)

diagnostics.build=If you''re having difficulty integrating the glossary generation into your document build, try Incorporating makeglossaries or makeglossaries-lite or bib2gls into the document build.

Remember that you need to rerun LaTeX after generating the glossary files. diagnostics.query_one=Would you like to {0}? diagnostics.query_two=Would you like to {0} or {1}? diagnostics.test_script=test {0} script diagnostics.clear_test_results=Clear test results. diagnostics.test_successful=It seems that {0} is correctly installed. diagnostics.no_indexer=Use the Settings menu to set the correct path to the {0} executable. diagnostics.no_language=The language is missing for glossary {0}. Have you accidentally done |GlsSetXdyLanguage|[{0}]'{}' or xindy='{'language='}'? I''ve used the fallback {1} instead. diagnostics.language_no_glossary=Check you have spelt the name of the glossary label correctly when using |GlsSetXdyLanguage|[{1}]'{'{0}'}' or check that you have defined glossary {1}. diagnostics.codepage_no_glossary=Check you have spelt the name of the glossary label correctly when using |GlsSetXdyCodePage|[{1}]'{'{0}'}' or check that you have defined glossary {1}. diagnostics.no_codepage=You need to specify the code page for the {0} glossary (e.g. utf8 or latin1) either using the inputenc package or setting it via |GlsSetXdyCodePage|[{0}]'{'codepage'}'. I''ve used the fallback {1} instead. diagnostics.unknown.encoding=I don''t recognise the encoding label ''{0}'' (or your Java Virtual Machine doesn''t support it). diagnostics.doc_indexer_encoding_mismatch=The indexer encoding ''{0}'' doesn''t seem to match {1,choice,1#the document encoding|1{0}. diagnostics.bad_attributes=The file {0} doesn''t seem to be a valid {1} style file. When you set the style name, make sure you use |SetStyleFile| instead of redefining |istfilename| and avoid using |glsxindytrue| or |glsxindyfalse|. diagnostics.no_entries=There were no entries listed for glossary {0}. Remember that you must index entries for them to appear in the glossary using the commands provided by the glossaries package. Entries that have been defined but not indexed won''t be listed. Check the following:

Have you used commands like |gls| or |glsadd| in the document? (If you haven''t, you need to add them.)
If you have used commands like |glsadd| or |glsaddall| in the preamble, have you remembered to put them after |makeglossaries|
If you have cross-referenced entries (for example, you have only referenced an entry in the description of another entry) you may need to retry making the glossaries after you have rerun LaTeX.
If you have at least version 4.24 of the glossaries package, have you used the debug option? (That might provide some more information for me to analyse.)

If you don''t want to index entries, you may want to consider using |printunsrtglossary| provided by glossaries-extra instead. diagnostics.no_entries_main=There were no entries listed for the main glossary. Remember that you must index entries for them to appear in the glossary using the commands provided by the glossaries package. Entries that have been defined but not indexed won''t be listed. If you don''t want to use this glossary, add the nomain package option to your document. Check the following:

Have you used commands like |gls| or |glsadd| in the document? (If you haven''t, you need to add them.)
If you have used commands like |glsadd| or |glsaddall| in the preamble, have you remembered to put them after |makeglossaries|?
If you have at least version 4.24 of the glossaries package, have you used the debug option? (That might provide some more information for me to analyse.)

If you don''t want to index entries, you may want to consider using |printunsrtglossary| provided by glossaries-extra instead. diagnostics.app_err={0} reported the following:

{1}

diagnostics.app_err_null=I''m stumped. Nothing was detected on the error output stream. diagnostics.unknown_language_or_codepage=Xindy doesn''t have a module for the combination of language {0} and codepage {1}. Use |GlsSetXdyLanguage| and/or |GlsSetXdyCodePage| to select the closest matching known language and codepage combination. diagnostics.io_error=An I/O error occurred. Use the Settings menu to check the paths to makeindex and xindy are correct, and check that the applications have the correct permissions. If you are using xindy, make sure that you also have Perl installed. diagnostics.interrupt=Something interrupted the process thread. diagnostics.no_ist=The style file can''t be found. If you have used |noist|, you have to supply your own style file. diagnostics.empty_sort=Xindy won''t accept the sort value {0} (for entry {1}) as it''s treated as an empty string. This is because xindy ignores (La)TeX commands within the sort field, so once all commands have been stripped from {0} the sort field becomes empty. You will need to explicitly set the sort field using the sort key in the entry definition. Alternatively, you may prefer to use |glsxtrnewsymbol| provided by the symbols package option with glossaries-extra to define symbols (which uses the label as the sort value) or consider using bib2gls instead of xindy. diagnostics.deprecated=You seem to be using a very old version of glossaries.sty. This may cause some complications from bugs or limitations associated with that version. I recommend you upgrade using your TeX distribution manager. diagnostics.oldversion=You are using version {0} ({1}) of glossaries.sty. There have been some bug fixes in newer versions that may have addressed some issues you might be facing. I recommend you upgrade using your TeX distribution manager. diagnostics.wrong_type=It looks as though you might have done something like |printglossary|[type='{'{0}'}'], but there''s no {0} glossary. diagnostics.wrong_type_noidx=It looks as though you might have done something like |printnoidxglossary|[type='{'{0}'}'], but there''s no {0} glossary. diagnostics.no_log=I can''t find the log file

{0}

so I can''t search for any more problems. diagnostics.multi_aux=There are multiple .aux files listed in the directory

{0}

Have you selected the correct file? (The base name should be the same as for the main .tex file or matching the -jobname option.) diagnostics.doc_defs=It seems you have defined terms in the document rather than in the preamble. This can cause complications. If you really want them in the document, you may need to delete the file

{0}

if something goes wrong or rebuild the document after making any modifications to the entry definitions. Remember that you can define terms in a separate file and load them using |loadglsentries|'{'filename'}' or |input|'{'filename'}'. If you really want document definitions, you can switch off this message using the Settings menu or consider using the glossaries-extra package with the docdef=restricted option. diagnostics.missing_lang=You don''t have any glossaries support for language {0}. This could simply mean that you need to install glossaries-{0} using your TeX package manager. However, if glossaries-{0} isn''t listed (or https://ctan.org/pkg/glossaries-{0} doesn''t exist), it most likely means {0} isn''t supported, in which case see section 1.4 (Multi-Lingual Support) of the glossaries user manual for further help. diagnostics.missing_sty=The package {0} is required but doesn''t seem to be installed. Use your TeX package manager to install it. If your package manager can''t find it, try searching for it on CTAN http://ctan.org/search/?phrase={0} diagnostics.missing_datatool_base=The package datatool-base is required but doesn''t seem to be installed. This package is part of the datatool bundle. If you already have datatool installed it could be that you have an old version that doesn''t include datatool-base.sty. Use your TeX package manager to install or update datatool. diagnostics.noidx=It seems you''ve used |makenoidxglossaries|, which means you don''t need xindy or makeindex, you just need a second LaTeX run to get the glossary up to date. (This is quite a slow and unreliable method of sorting and indexing. You may want to consider using |printunsrtglossary| provided by glossaries-extra instead. See the glossaries performance page for a comparison.) diagnostics.bib2gls=It seems you''ve used |GlsXtrLoadResources| (or |glsxtrresourcefile|), which means you need to run

bib2gls -g {0}

(you may omit the -g switch if you don''t require letter groups) and then rerun LaTeX. You don''t need makeindex or xindy for this document. diagnostics.bib2gls_norecords=No records were found in the .aux file. Have you remembered to use the record package option? If you want all entries selected, remember to use selection=all in |GlsXtrLoadResources| not |glsaddall| or |glsaddallunused|. diagnostics.missing_glstex=bib2gls is needed to create the missing file ''{0}'' to resolve undefined entry warnings. (Only one bib2gls call is required to create all .glstex files for the document if you have multiple resource sets.) diagnostics.missing_glstex_hybrid=bib2gls is needed to create the missing file ''{0}''. (Only one bib2gls call is required to create all .glstex files for the document if you have multiple resource sets.) Since you are using a hybrid bib2gls/makeglossaries document, the indexing can''t be performed until this file has been created. diagnostics.bib2gls_build=The complete build process is:

{0} {1}\nbib2gls -g {1}\n{0} {1}

(The -g switch may be omitted if you don''t require letter groups.) diagnostics.hybrid_build=The complete build process is:

{0} {1}\nbib2gls -g {1}\n{0} {1}\n{2} {1}\n{0} {1}

(The -g switch may be omitted if you don''t require letter groups.)

Are you sure you want this hybrid approach? bib2gls can sort and collate. The hybrid approach is only necessary if you have a specific xindy rule that can''t be replicated by bib2gls''s custom sort rule or if you require particular xindy location classes or location types in an order that''s counter to the document page ordering. If you are happy to just use bib2gls then change the package option record=alsoindex to record=only (or just record), remove |makeglossaries| and replace |printglossary| with |printunsrtglossary|. diagnostics.shell_disabled=It seems that TeX refused to run the system command

{0}

because the shell escape had been disabled. diagnostics.shell_restricted=It seems that TeX refused to run the system command

{0}

because the restricted mode was on and {1} isn''t on the list of trusted applications. You will need to incorporate the {1} call as part of your document build process.diagnostics.no_glossaries=The document doesn''t define any glossaries. Have you used the nomain option by mistake? diagnostics.undef_cs=LaTeX reported an undefined control sequence. Perhaps you''re trying to use a command that has been introduced in a later version of one of the packages you''re using. If this is the case, you''ll need to use your TeX package manager to update the relevant package. Alternatively, you may simply have misspelt the command or forgotten to define it or forgotten to load the package that provides it. Details:

{0}

diagnostics.undef_indexspace=It seems that |indexspace| hasn''t been defined. This suggests you''re using an old version of glossaries with a class that doesn''t define this command. I recommend you upgrade to a newer version of glossaries using your TeX package manager. diagnostics.too_long={0,number,integer} {0,choice,1#entry was|1sort field or label for {0,number,integer} {0,choice,1#that entry|1{0}. This may be because that option was introduced to a later version, in which case you will need to use your TeX package manager to update the glossaries package, or it may be that you have misspelt the option. diagnostics.dry_run=Dry run mode on. System command would''ve been: diagnostics.wrglossary=It seems you have tried to index an entry in the {0} glossary on line {1}, but the associated file hasn''t been opened. Remember to use |makeglossaries| before commands like |glsadd| and |glsaddall|. Details of lost indexing code: diagnostics.mapped_lang=Your document has requested that xindy be run with language ''{0}''. This is a babel or polyglossia language identifier. I''m going to assume you meant the xindy language module ''{1}''. diagnostics.variant=Your document has requested that xindy be run with codepage ''{1}'', but language ''{0}'' requires additional information. I''m going to assume you meant ''{2}-{1}'' for the codepage. (Use Dry Run Mode to find the exact call to xindy.) diagnostics.no_aux=Since the aux file doesn''t exist, there''s not much I can do to help, but I''ll parse the log file in case there are any clues there. diagnostics.fragile=It''s possible that there''s an expansion issue involving a fragile command. Things to check for:

Have you used a class like beamer that doesn''t make common formatting commands like |textit| robust?
Have you tried using |protect| in front of fragile commands contained within your entry definitions?
Have you tried switching off the expansion using commands like |glsnoexpandfields|? (See section 4.6 Expansion in the glossaries user manual.)

diagnostics.inputenc=There''s a Unicode character error message from the inputenc package. This may or may not be related to any issues you might be having with the glossaries package, but remember that if you want to have non-ASCII characters in your entry labels (such as accented letters) you must use XeLaTeX or LuaLaTeX. diagnostics.labels_with_problem_char={0,number,integer} {0,choice,1#entry|1{1} {0,choice,1#contains|1|include|'{'{0}'}' in the preamble. Remember that |include| should only be used within the document environment. I recommend you use |input|'{'{0}'}' instead. (See also Why shouldn''t I use |include| to include my glossary definitions?) diagnostics.ist_in_log=The indexer information has been written to the .log file instead of the .aux file. This suggests that the .aux file wasn''t available when it was written. The most probable cause is that |makeglossaries| has been placed in a file that has been read using |include| instead of |input|. diagnostics.problem_group_label=There seems to be a problem with the letter group label {0}. The label is used to construct a command name, so it can''t contain any special characters. (This includes extended characters if you''re using inputenc.sty.) diagnostics.suggest_bib2gls=You may want to consider using bib2gls instead. diagnostics.suggest_unicode_or_bib2gls=You may want to consider using xindy with a LaTeX engine that has native Unicode support (XeLaTeX or LuaLaTeX) or use bib2gls instead. diagnostics.at_least_version=You need at least version {0} of {1}. diagnostics.makeglossdisabled=The ''disablemakegloss'' option was in effect when |makeglossaries| or |makenoidxglossaries| was used on line {0}. diagnostics.makeglossrestored=The ''restoremakegloss'' option was used to restore |makeglossaries| or |makenoidxglossaries| on line {0}. diagnostics.restoremakegloss=You need to use the ''restoremakegloss'' option to cancel the effect of ''disablemakegloss''. diagnostics.restoremakegloss.cancelled=It seems that the effect of ''restoremakegloss'' was later cancelled by ''disablemakegloss''. diagnostics.restoremakegloss.late=It may be that you have used ''restoremakegloss'' too late to cancel ''disablemakegloss'' or you have forgotten to add |makeglossaries| after ''restoremakegloss''. # Properties dialog properties.title=Preferences properties.start_dir=Start Up Directory properties.start_dir.mnemonic=S properties.dir.home=Home properties.dir.home.mnemonic=H properties.dir.last=Last Used Directory properties.dir.last.mnemonic=L properties.dir.custom=Custom: properties.dir.custom.mnemonic=U properties.override=Override document language settings properties.override.mnemonic=R properties.applications=Applications properties.applications.mnemonic=A properties.makeindex=Path to Makeindex: properties.makeindex.mnemonic=M properties.xindy=Path to Xindy: properties.xindy.mnemonic=X properties.german_word_order=German Word Order properties.german_word_order.mnemonic=G properties.language=Language properties.language.mnemonic=G properties.encoding=Encoding properties.encoding.mnemonic=E properties.diagnostics=Diagnostics properties.diagnostics.mnemonic=D properties.docdefcheck=Check for document definitions properties.docdefcheck.mnemonic=D properties.langcheck=Check for missing language modules properties.langcheck.mnemonic=M properties.gui=GUI properties.gui.mnemonic=G properties.font.sample=Sample Text properties.font=Font properties.font.mnemonic=F properties.bold.font=Bold properties.bold.font.mnemonic=B properties.italic.font=Italic properties.italic.font.mnemonic=I properties.size.font=Size properties.size.font.mnemonic=Z properties.look_and_feel=Look and Feel properties.look_and_feel.mnemonic=K properties.restart=(restart required) # batch mode messages message.loading=Loading ''{0}'' message.found=Found {0} # Error messages error.title=Error error.io.file_doesnt_exist=File ''{0}'' doesn''t exist. error.no_such_file=File not found. error.no_xindy=Can''t find Xindy application. error.no_makeindex=Can''t find Makeindex application. error.no_makeglossaries=Can''t find {0} script. Is glossaries.sty installed and up-to-date? error.missing_application=Can''t find {0} on the system path (PATH={1}). Have you installed {0}? error.no_perl=Perl is required to run {0}. error.no_glossaries=No glossaries defined. error.invalid_order=Invalid order ''{0}'' (must be either ''letter'' or ''word''). error.missing_order=Missing order. error.missing_ist=Missing style file. error.cant_determine_indexer=Can''t determine indexer. error.bib2gls_indexer=This document requires bib2gls not makeindex or xindy. error.unknown=Unknown error.missing_dir_name=Missing directory name. error.no_such_directory=''{0}'' doesn''t exist or isn''t a directory. error.no_language=Missing language for glossary ''{0}''. error.no_codepage=Missing codepage for glossary ''{0}''. error.language_no_glossary=Language is set to ''{0}'' for glossary ''{1}'', but no such glossary exists. error.codepage_no_glossary=Codepage is set to ''{0}'' for glossary ''{1}'', but no such glossary exists. error.entries_rejected={0,number,integer} {0,choice,1#entry was|1