> the output is already nice! a few glitches: > > 1. '\n' newlines are not correctly detected - compare LFUN_PARAGRAPH_PARAMS of > the current trunk and your output.
This problem is due to the dact that the LFUN_PARAGRAPH_PARAMS comment contains this string "\\no" (I can't remember the rest sorry) and my script finds the "\n" and creates a newline. Looking at this exposed a falw in the doxygen comments that are used in LyXAction.cpp. Are they supposed to be written as if a C++ string literal with "\" escaped by having "\\" where the output should be a "\"? This is donw in some cases (as seen above in the PARAGRAPH_PARAMS example) but not in others. It's hard to work round the inconsistent behaviour. > 2. links to various LFUNS are denoted with #LFUN_xxx (eg see description > of LFUN_CHAR_LEFT_SELECT). '#' should be deleted (or even crossreferenced - > but this is quite advanced thing, not desperatelly needed - only if you are > bored enough ;) I've added a line to replaece all occurrences of "#LFUN" with just "LFUN" > 3. as you already noted there is a problem with long parameter lines > containing > '|'. i see several ways how to fix them - either to write some parsing > function > which recognized line with the list of '|' and break it with some whitespace > after 80 chars or so. second possibility would be to put this whitespace > directly > into lyxaction.cpp, although i dont like this solution much... I'll look into this when I get a chance > > 4. send us please gpl statement eg. > http://marc.info/?l=lyx-devel&m=118765575314017 Again, on my TODO list! I've also added support for the 'sample' field which I had completely overlooked in the first version of the script. The next version is nearly ready but I've just got a few more things to change. Should I post it to the trac entry of the bug when done or attach it to an email to the list? I don't fancy emailing it to the list as the code is quite long with the hardcoded .lyx file header as a string literal! Just as a heads-up I don;t knoe ANYTHING about buildsystems or tools like make so I won't be able to write diffs which hook the script into the build system, sorry. In a month or so when I am less busy I might be able to learn enough about make and cmake to do it, but not sooner. Thanks for your help in exposing the shortcomings of the script Ewan
