EVALUATION
Note that this is more than just a rename, as I believe -linksourcetab
originally performed -linksource as well as setting the tab.
The new -sourcetab option would only set the tab and not perform
any function to generate the source files in HTML.
###@###.### 2002-12-05
This option certainly applies to the standard doclet, as
browsers treat tab characters as if they were a single character.
MIF Doclet users would be less likely to use this option,
as they might want keep the tabs present in the source file.
The following doc comment contains tabs.
/**
* This line has an asterisk and two tabs to its left and ends with <br>.<br>
This line has no asterisks and one tab to its left.
*/
The tabs on the following first line seem to be stripped out by the standard doclet. The tab on the second line appears to be converted to 8 spaces.
Is this value of 8 hard-coded in the standard doclet? YES
<DD>This line has an asterisk and two tabs to its left and ends with <br>.<br>
This line has no asterisks and one tab to its left.
###@###.### 2002-12-05
When -sourcetab is implemented, it should convert tabs to spaces mod the
tab's position on the line. That is, it should insert enough spaces
to move the cursor to the next "virtual" tab stop. So -sourcetab
would insert 8 spaces if the tab is at the start of the line, but
only 7 spaces if the line starts with space/tab. This will make the
spacing line up in <pre> text.
###@###.### 2003-07-19
Because the developer might be using tabs to align columns similar to
a table outside of <PRE> text, these tabs should be converted to spaces
globally throughout the doc comments.
###@###.### 2003-07-22
Suggestion for the -help text is:
-sourcetab <tab-length> Specify number of spaces each tab takes up in source
###@###.### 2004-01-24
Fixed. The -sourcetab is now enabled and replaces the -linksourcetab option.
###@###.### 2004-03-29
|
Java