Issues in man pages of bison (part 2)
Helge Kreutzmann <[email protected]> Sun, 18 Jan 2026 06:42:17 +0000
| Newsgroups | gmane.comp.parsers.bison.bugs |
|---|---|
| Message-ID | <[email protected]> |
This is a MIME-formatted message. If you see this text it means that your
E-mail software does not support MIME-formatted messages.
--=_meinfjell-2938297-1768718537-0001-2
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Dear Bison maintainer,
the manpage-l10n project[1] maintains a large number of translations of
man pages both from a large variety of sources (including Bison) as
well for a large variety of target languages.
During their work translators notice different possible issues in the
original (english) man pages. Sometimes this is a straightforward
typo, sometimes a hard to read sentence, sometimes this is a
convention not held up and sometimes we simply do not understand the
original.
We use several distributions as sources and update regularly (at
least every 2 month). This means we are fairly recent (some
distributions like archlinux also update frequently) but might miss
your latest upstream version once in a while, so the error might be
already fixed. We apologize and ask you to close the issue immediately
if this should be the case, but given the huge volume of projects and
the very limited number of volunteers we are not able to double check
each and every issue.
Secondly we translators see the manpages in the neutral po format,
i.e. converted and harmonized, but not the original source (be it man,
groff, xml or other). So we cannot provide a true patch (where
possible), but only an approximation which you need to convert into
your source format.
Finally the issues I'm reporting have accumulated over time and are
not always discovered by me, so sometimes my description of the
problem my be a bit limited - do not hesitate to ask so we can clarify
them.
I'm now reporting the issues for your project. If future reports
should use another channel, please let me know.
[1] https://manpages-l10n-team.pages.debian.net/manpages-l10n/
Man page: bison.1
Issue: to be divided in two paragraphs and attached with next one
"B<-M>, B<--file-prefix-map>=3DI<\\,OLD=3DNEW\\/> replace prefix OLD with N=
EW when writing file paths"
--
Man page: bison.1
Issue 1: I<Bison> =E2=86=92 B<Bison>
Issue 2: I<yacc>(1) =E2=86=92 B<yacc>(1)
Issue 3: I<yacc> =E2=86=92 B<yacc>
"I<Bison> is a parser generator in the style of I<yacc>(1). It should be "
"upwardly compatible with input files designed for I<yacc>."
--
Man page: bison.1
Issue 1: I<yacc> =E2=86=92 B<yacc>
Issue 2: B<.y> =E2=86=92 I<.y>
Issue 3: .ypp or .y++ =E2=86=92 I<.ypp> or I<.y++>
Issue 4: bison =E2=86=92 B<bison>
Issue 5: .cpp or .c++ =E2=86=92 I<.cpp> or I<.c++>
Issue 6: B<parse.yxx> =E2=86=92 I<parse.yxx>
Issue 7: B<parse.tab.cxx> =E2=86=92 I<parse.tab.cxx>
Issue 8: B<y.tab.c> =E2=86=92 I<y.tab.c>
Issue 9: I<Bison> =E2=86=92 B<bison>
Issue 10: B<parse.tab.c> =E2=86=92 I<parse.tab.c>
"Input files should follow the I<yacc> convention of ending in B<.y>. Unli=
ke "
"I<yacc>, the generated files do not have fixed names, but instead use the "
"prefix of the input file. Moreover, if you need to put I<C++> code in the=
"
"input file, you can end his name by a C++-like extension (.ypp or .y++), "
"then bison will follow your extension to name the output file (.cpp or .c+"
"+). For instance, a grammar description file named B<parse.yxx> would "
"produce the generated parser in a file named B<parse.tab.cxx>, instead of "
"I<yacc>'s B<y.tab.c> or old I<Bison> version's B<parse.tab.c>."
--
Man page: bison.1
Issue 1: I<bison> =E2=86=92 B<bison>
Issue 2: B<bison.texi> =E2=86=92 I<bison.texi>
"This description of the options that can be given to I<bison> is adapted "
"from the node B<Invocation> in the B<bison.texi> manual, which should be "
"taken as authoritative."
--
Man page: bison.1
Issue: I<Bison> =E2=86=92 B<Bison>
"I<Bison> supports both traditional single-letter options and mnemonic long=
"
"option names. Long option names are indicated with B<--> instead of B<->.=
"
"Abbreviations for option names are allowed as long as they are unique. Wh=
en "
"a long option takes an argument, like B<--file-prefix>, connect the option=
"
"name and the argument with B<=3D>."
--
Man page: bison.1
Issue: tracing same as =E2=86=92 tracing, same as
"instrument the parser for tracing same as '-Dparse.trace'"
--
Man page: bison.1
Issue: NAME in italics?
"B<-D>, B<--define=3DNAME>[=3DI<\\,VALUE\\/>]"
"B<-F>, B<--force-define=3DNAME>[=3DI<\\,VALUE\\/>]"
msgstr "B<-F>, B<--force-define=3DNAME>[=3DI<\\,WERT\\/>]"
--
Man page: bison.1
Issue: leave =E2=86=92 write
"leave output to FILE"
msgstr "Schreibt Ausgabe in DATEI."
--
Man page: bison.1
Issue: info bison =E2=86=92 B<info bison>
"For complete documentation, run: info bison."
--
Man page: bison.1
Issue: B<info> =E2=86=92 B<info>(1)
"The full documentation for B<bison> is maintained as a Texinfo manual. If=
"
"the B<info> and B<bison> programs are properly installed at your site, the=
"
"command"
--=20
Dr. Helge Kreutzmann [email protected]
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
--=_meinfjell-2938297-1768718537-0001-2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEEbZZfteMW0gNUynuwQbqlJmgq5nAFAmlsgMAACgkQQbqlJmgq
5nDESRAAnuK2SjwXZPr4Fg8zq9wl75Y9RlYndRBSkmJErfYIuTj9pVY/5r5ocJvV
eX25AHQU8Fg77aVRawKad92mZRIthCqS05l47xFu+j8r6jM8oi2c8OMv5xIv1ls7
OGZU2nk0GMy9zOX1UHsKLDgzwkwNU9uWMpDxqwnmgpMVYNnlBXtSeWuFipkgLW/U
jLgM4s06oVlfMMgGREkFmAo+DuKcnoeqor6a9yqO+CTNSd3fUFkeqt5m98tCYlcM
DLoBZOqlNNsEQNoc1hyUYvsruF8yuM000BOfoxrbkaT+6I5sMJINLWhHMgHft6Jp
BZOJflFe8Rqh+ywDx1JXqJiUCjlkVFvIKHINba55bn7Q7ZAdmn2SWrEbGFFGcnlj
YzK/5NMqnEuiu/SanNVRYF7KJmzPSkx0dzLNMxe0ECfKjVavZe3rem6mOOndBDUB
/nfCUWK6WG/PjatwgeGOodokmRjf0VYnHd0lPWEZ/y7L6enERiHNNJOqr7JGNM5I
rAppIYWkDm4bYzQ/Ey4tLRfeGLVA751PBkc+hljIFG1VrQkPz6BBxUvNVlZsmtg7
A9I9yxjnlbLsx73li8NYcGYVkpr+f52w9vVXGC3XLU5aQmiOVBERSAxqvjNwgUV9
bob0qtNfkD4yRBHn29pWWZm+swNwtCZpUyY9B5yHqEPzQQva3zM=
=gbdK
-----END PGP SIGNATURE-----
--=_meinfjell-2938297-1768718537-0001-2--