#119 outdated hyperlink for [8]

feature request
closed-fixed
Gerwin Klein
5
2013-10-20
2012-02-22
mranderson2007
No

Discussion

  • mranderson2007
    mranderson2007
    2012-02-22

    btw: can you please recreate manual.html with the same settings as before, but with LaTeX2HTML 2008 (instead of the older LaTeX2HTML 2002-2-1). This fixes especially a bug that caused a line "<tex2html_verbatim_mark>mathend000#" to appear in the resulting html file, making it invalid.

     
  • mranderson2007
    mranderson2007
    2012-02-23

    Another minor thing in the manual, not worth opening a new separate report:

    > TraditionalComment is the expression that matches the string "/*" followed by a character that is not a *, followed
    > by anything that does not contain, but ends in "/*".

    If I do not completely misunderstand that paragraph, it should read

    > …but ends in "*/".

    (the comment closing token */ instead of /*)

     
  • mranderson2007
    mranderson2007
    2012-02-29

    Finally, I have read the whole manual and found some more typos and other trivial issues:

    4.1, page 13
    > It is possible, but not considered as good Java programming style to put own helper class
    > (such as token classes) in this section.
    class --> classes

    4.2.3, page 16
    > The default end of file values depends on the return type of the scanning method:
    values --> value

    4.2.7, page 19
    > After unpacking the internal access to the DFA table is exactly the same as with
    > option %table
    unpacking the --> unpacking, the

    4.2.11, page 21
    > State declarations have the following from:
    from --> form

    4.3, page 22
    > The “lexical rules” section of an JFlex specification contains
    an --> a

    4.3.1, page 22
    > The syntax of the ”lexical rules” section is described by the following BNF grammar
    BNF --> EBNF
    (Actually this is also not true if you refer to the original EBNF from Niklaus Wirth. However, modifications to EBNF are quite common, whereas BNF is usually exactly used as it was originally defined for ALGOL 60)

    4.3.2, page 25
    > a | b (union)
    > is the regular expression, that matches all input that is matched by a or by b.
    > a b (concatenation)
    > is the regular expression, that matches the input matched by a followed by the input matched by b.
    expression, that --> expression that
    (two times)

    4.3.2, page 26
    > So a$ is equivalent to a / \r|\n|\r\n|\u2028|\u2029|\u000B|\u000C|\u0085.This is a bit
    \u0085.This --> \u0085. This
    (space missing)

    4.3.4, page 28
    > (in which case the scanning method return with this value)
    return --> returns

    4.3.5, page 29
    > They will be remain stable and supported between JFlex releases as long as possible.
    will be remain stable --> will remain stable

    4.3.5, page 30
    >The pushed back characters will after the call of yypushback not be included in yylength and yytext().
    This sentence should be revised: yytext() has its brackets, while the other two methods do not. Also, I suggest moving "after the call of yypushback" to the front of the sentence.

    5.2, page 32
    > for instance, when you scan a HTML page, it may have embedded information
    a --> an

    6.2, page 35
    > "averylongkeyword"
    >.
    the dot is not indented, but probably it should be, because it is an element of the set

    6.2, page 36
    > (when the last character read is \r the scanner has to read one character ahead to
    > check if the next one is an \n or not).
    is \r the scanner --> is \r, the scanner

    7.2.3, page 39
    > This should usually cause not much problems,
    cause not --> not cause

    8.1, page 39
    > One of the main design goals of JFlex was to make interfacing with the free Java parser
    > generator CUP [8] as easy as possibly.
    possibly --> possible

    8.1.1, page 39
    > JFlex lexers now implement this interface automatically when then %cup switch is used.
    then --> the

    8.1.1, page 39
    > If your generated lexer has the class name Scanner, the parser is started
    > from the a main program like this:
    from the a main program --> from the main program

    8.1.2, page 40
    > You can do so either by using an %eofval{ directive or by using and <<EOF>> rule.
    and --> an

    8.1.3, page 40
    > This means, that the scanning function now changes
    means, that --> means that

    8.1.4, page 41
    > For people, who like or have to use older versions of CUP,
    people, who like --> people who like

    8.1.4, page 41
    > Please note, that the standard name
    Please note, that --> Please note that

    8.2, page 43
    > For a small calculator example, one could use a set up like the following
    set up --> setup

     
  • Gerwin Klein
    Gerwin Klein
    2012-02-29

    Thanks for the extensive feedback!

    Cheers,
    Gerwin

     
  • Gerwin Klein
    Gerwin Klein
    2013-10-20

    These are now all fixed in rev 669.

     
  • Gerwin Klein
    Gerwin Klein
    2013-10-20

    • status: open --> closed-fixed
    • Group: --> feature request