tetex-bin/base: Please review our changed templates files
Dear english translation team,
We have added or changed a couple of debconf questions. Since none of
the tetex maintainers is a native english speaker, and before pestering
translators to update the translations for sarge, I would be glad if you
could have a look at those files.
I don't want to urge you, but I'd be really glad if you'd inform me if
currently nobody has time to have a look, so that I don't wait in vain.
The templates files are attached.
Thank you in advance, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
Template: tetex-base/oldupdm
Type: note
_Description: Remove old updmap?
tetex-base has found /etc/texmf/dvips/updmap from a previous version of
tetex-base. You seem to have modified this script.
.
This script is no longer included in current tetex-base and should not be
used. It will be renamed to updmap.postinst-old.
.
Changes like the ones you made to this script should now be made to files
in /etc/texmf/updmap.d/, see the manpage for update-updmap.
Template: tetex-base/olddat
Type: boolean
Default: true
_Description: Remove old dat files for texdoctk?
Old dat files for texdoctk from a previous version of tetex-base were
found. The files are texdoc-100.dat, texdoc-102.dat, and texdoc-103.dat
in /etc/texdoctk/, and they were used only in a teTeX beta version.
.
If you think you have modified any of them, then you may refuse this option
and preserve them. But, for almost 99% of you, it is strongly recommended
to remove these files right now!
Template: tetex-base/fmtutil-failed
Type: note
_Description: TeX format generation failed
The generation of some of the format files needed to run TeX, LaTeX
etc. has failed. You will not be able to run those programs until
this is fixed.
.
One frequent cause for such a failure is that a new version needs
changed configuration files, but you did not accept the maintainers'
version of a file you manually changed.
.
If you report a bug, please include the output of fmtutil, stored in
${fmtutil_tempfile}
Template: tetex-base/updmap-failed
Type: note
_Description: generation of TeX font information failed
The generation of the font map files by the updmap script
failed. Therefore, TeX, LaTeX etc. will have problems finding the
font files they need.
.
If you report this as a bug, please include the output of updmap,
stored in ${updmap_tempfile}
Template: tetex-bin/fmtutil
Type: boolean
Default: true
_Description: Use update-fmtutil to automatically generate fmtutil.cnf?
The file fmtutil.cnf is the central configuration file for TeX engines.
Automatic generation is recommended to make the setup work with other TeX
related packages.
.
To customize your setup, you should not edit fmtutil.cnf directly but
instead modify the files in /etc/texmf/fmt.d/. The generated fmtutil.cnf
will then be placed under /var/lib/texmf/web2c.
.
Don't accept this if you want to keep using an existing fmtutil.cnf.
Then you have to modify /etc/texmf/fmtutil.cnf manually.
REMARK: Installation of some TeX-related packages will fail in this case.
Template: tetex-bin/upd_map
Type: boolean
Default: true
_Description: Use update-updmap to automatically generate updmap.cfg?
The file updmap.cfg is the central configuration file for the fonts
system of TeX. Automatic generation is recommended to make the setup work
with font packages of TeX.
.
To customize your setup, you should not edit updmap.cfg directly but
instead modify the files in /etc/texmf/updmap.d/. The generated updmap.cfg
will be placed under /var/lib/texmf/web2c.
.
Don't accept this if you want to keep using an existing updmap.cfg. Then you
should modify /etc/texmf/updmap.cfg manually.
REMARK: Automatic installation of TeX fonts will fail in this case.
Template: tetex-bin/lsr-perms
Type: boolean
Default: true
_Description: Use debconf to manage permissions of ls-R files?
A lot of font files have to be generated before they can be used by
teTeX's display and printing programs, like xdvi, dvips etc. Those
files are stored in /var/cache/fonts, so that they do not need to be
regenerated every time. ls-R files tell the system which files are
stored yet, and where.
.
Accepting this option will allow you to easily manage the permissions of
those ls-R files using debconf. Otherwise you will have to manually
ensure that they get useful but safe permissions.
Template: tetex-bin/groupname
Type: string
Default: users
_Description: Which group should own the ls-R files?
Modification of ls-R files can be restricted to the members of one group
which owns them. To take advantage of this, add the users to the group of
your choice, and enter that group name here. The default group 'users' is
appropriate for most systems.
Template: tetex-bin/groupperm
Type: boolean
Default: true
_Description: Allow group members to modify ls-R files?
Accepting this option will allow members of the owning group to modify the
ls-R files. Almost everybody should accept this option!
Template: tetex-bin/userperm
Type: boolean
Default: false
_Description: Allow all users to modify ls-R files?
Accepting this option will allow all users to modify ls-R files. This is
generally not a good idea for security reasons; you should instead
restrict such access to members of one group.
Template: tetex-bin/cnf_name
Type: note
_Description: Name change of files in /etc/texmf/texmf.d/
texmf.cnf has previously been generated by update-texmf from all files
in /etc/texmf/texmf.d/. Now update-texmf is changed and only reads
files with extension '.cnf'
.
So if you had any private file in /etc/texmf/texmf.d/, then you should add
'.cnf' to its name; for example, 22mymacro => 22mymacro.cnf
Template: tetex-bin/oldcfg
Type: boolean
Default: true
_Description: Remove old and harmful file /etc/X11/Xresources/tetex-base?
An old version of tetex-bin installed /etc/X11/Xresources/tetex-base,
but it is now not used and even harmful if it exists. It is
strongly recommended to let the installation script remove this file
right now!
.
Remove this file?
Template: tetex-bin/use_debconf
Type: boolean
Default: false
_Description: Manage language.dat with debconf?
The language.dat file, which contains the information which hyphenation
patterns will be available, can be handled by debconf.
.
If you do not choose this, one pattern set for each supported
language will be enabled (two for german, with old and new
orthography). You can choose debconf management if you want to
exclude some patterns and get smaller (La)TeX format files. Manual
editing is still possible, and your changes will be preserved.
Template: tetex-bin/hyphen
Type: multiselect
Choices: bahasa, basque, catalan, croatian, czech, danish, dutch, finnish, french[=patois], german[=austrian-alte_Rechtschreibung], ngerman[=naustrian-neue_Rechtschreibung], greek, icelandic, irish, italian, latin, magyar, norsk[old], norsk[nohyphb.tex], norsk[nohyphbc.tex], polish, portuges, romanian, russian, slovak, slovene, spanish, swedish, turkish, ukrainian[ukrhyph.tex], ukrainian[ukrhyph.t2a], ukrainian[ukrhyph.lcy], ukrainian[ukrhyph.ot2]
Default: french[=patois], ngerman[=naustrian-neue_Rechtschreibung]
_Description: Which hyphenation patterns should be loaded?
If you want to load extra hyphenation pattern(s) please select them
from the list.
.
If you want to change hyphenation pattern(s) to load afterwards, you can
do so with "dpkg-reconfigure tetex-bin" and select any hyphenation pattern
you like. Manual editing is still possible, and your changes will be
preserved.
Template: tetex-bin/fmtutil-failed
Type: note
_Description: TeX format generation failed
The generation of some of the format files needed to run TeX, LaTeX
etc. has failed. You will not be able to run those programs until
this is fixed.
.
One frequent cause for such a failure is that a new version needs
changed configuration files, but you did not accept the maintainers'
version of a file you manually changed.
.
If you report a bug, please include the output of fmtutil, stored in
${fmtutil_tempfile}
Template: tetex-bin/updmap-failed
Type: note
_Description: Generation of TeX font information failed
The generation of the font map files by the updmap script
failed. Therefore, TeX, LaTeX etc. will have problems finding the
font files they need.
.
If you report this as a bug, please include the output of updmap,
stored in ${updmap_tempfile}
Reply to: