jankrause / idocit

Automatically exported from code.google.com/p/idocit
0 stars 0 forks source link

Formatting is lost when saving documentation #89

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Open an Java-Interface with an operation.
2. Add the text from below as the ACTION documentation.
3. Reopen the interface and view the ACTION documentation.

ACTION-Documentation:
<copy>
General description:
Use this call to retrieve the accumulated feedback left for a specified user, 
or the summary feedback data for a specific item listing or order line item.

If no input filters (UserID,ItemID,TransactionID,OrderLineItemID)are specified, 
the call returns the aggregate feedback score for the requesting user.

<noise sourcesection="Requestdetails">GetFeedback takes the following values as 
input filters: UserID, Item ID,TransactionID,or OrderLineItemID. See the Call 
Reference Input table for more information on these fields.</noise>

Test Cases:
You can test GetFeedback in the Sandbox environment.

For best results:

- Use a minimum of three test users. This allows for one test user to be the 
one whose feedback is returned and the others serve as participants in 
successfully ended listings. Have different test users leave multiple feedback 
scores for the target user.

- Test GetFeedback on a new test user who does not yet have any feedback. Also 
test for returning just summary feedback data as well as returning feedback 
details.

- Test GetFeedback on a test user or item with enough feedback entries to 
paginate the feedback detail data. For example,if you have a user with 20 
feedback records, use pagination to return 10 feedback records per call, and 
retrieve all records. Succeeding on this test ensures that the application is 
able to accommodate retrieving voluminous feedback with multiple sequential 
calls.
</copy>

What is the expected output? What do you see instead?
I expect the text and formatting from above, but I get this:

<copy>
General description:
Use this call to retrieve the accumulated feedback left for a specified user, 
or the summary feedback data for a specific item listing or order line item.
If no input filters (UserID,ItemID,TransactionID,OrderLineItemID) are 
specified, the call returns the aggregate feedback score for the requesting 
user.
<
noise sourcesection=
"
Requestdetails
"
>
GetFeedback takes the following values as input filters: UserID, Item 
ID,TransactionID,or OrderLineItemID. See the Call Reference Input table for 
more information on these fields.
<
/noise
>
Test Cases:
You can test GetFeedback in the Sandbox environment.
For best results:
- Use a minimum of three test users. This allows for one test user to be the 
one whose feedback is returned and the others serve as participants in 
successfully ended listings. Have different test users leave multiple feedback 
scores for the target user.
- Test GetFeedback on a new test user who does not yet have any feedback. Also 
test for returning just summary feedback data as well as returning feedback 
details.
- Test GetFeedback on a test user or item with enough feedback entries to 
paginate the feedback detail data. For example, if you have a user with 20 
feedback records, use pagination to return 10 feedback records per call, and 
retrieve all records. Succeeding on this test ensures that the application is 
able to accommodate retrieving voluminous feedback with multiple sequential 
calls. 
We have to see, what is done.
</copy>

Please note: this problem has to be fixed in general and not only for Javadoc.

Original issue reported on code.google.com by krauseda...@web.de on 22 Feb 2012 at 8:09

GoogleCodeExporter commented 9 years ago

Original comment by krauseda...@web.de on 23 Feb 2012 at 4:36

GoogleCodeExporter commented 9 years ago
Fixed this issue for Java: Improved handling with empty HTML elements, like 
<br/> and <tab/>.

Original comment by dirk.mei...@gmail.com on 3 Apr 2012 at 11:07

GoogleCodeExporter commented 9 years ago
Test this documentation for WSDL

Original comment by dirk.mei...@gmail.com on 3 Apr 2012 at 11:11

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r574.

Original comment by dirk.mei...@gmail.com on 3 Apr 2012 at 11:12

GoogleCodeExporter commented 9 years ago
WSDL keeps the formatting correctly.

Original comment by dirk.mei...@gmail.com on 3 Apr 2012 at 12:13

GoogleCodeExporter commented 9 years ago
It seems to work for Javadoc and WSDL. I close this issue.

Original comment by krauseda...@web.de on 13 Apr 2012 at 12:30