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>=I<\\,OLD=NEW\\/> replace prefix OLD with NEW when writing file paths" -- Man page: bison.1 Issue 1: I<Bison> → B<Bison> Issue 2: I<yacc>(1) → B<yacc>(1) Issue 3: I<yacc> → 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> → B<yacc> Issue 2: B<.y> → I<.y> Issue 3: .ypp or .y++ → I<.ypp> or I<.y++> Issue 4: bison → B<bison> Issue 5: .cpp or .c++ → I<.cpp> or I<.c++> Issue 6: B<parse.yxx> → I<parse.yxx> Issue 7: B<parse.tab.cxx> → I<parse.tab.cxx> Issue 8: B<y.tab.c> → I<y.tab.c> Issue 9: I<Bison> → B<bison> Issue 10: B<parse.tab.c> → I<parse.tab.c> "Input files should follow the I<yacc> convention of ending in B<.y>. Unlike " "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> → B<bison> Issue 2: B<bison.texi> → 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> → 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. When " "a long option takes an argument, like B<--file-prefix>, connect the option " "name and the argument with B<=>." -- Man page: bison.1 Issue: tracing same as → tracing, same as "instrument the parser for tracing same as '-Dparse.trace'" -- Man page: bison.1 Issue: NAME in italics? "B<-D>, B<--define=NAME>[=I<\\,VALUE\\/>]" "B<-F>, B<--force-define=NAME>[=I<\\,VALUE\\/>]" msgstr "B<-F>, B<--force-define=NAME>[=I<\\,WERT\\/>]" -- Man page: bison.1 Issue: leave → write "leave output to FILE" msgstr "Schreibt Ausgabe in DATEI." -- Man page: bison.1 Issue: info bison → B<info bison> "For complete documentation, run: info bison." -- Man page: bison.1 Issue: B<info> → 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" -- 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/
signature.asc
Description: PGP signature
