Huai Lei, thankyou for your work on these issues. :) On 02/07/2008, at 10:33 AM, chl.207 wrote:
I have confirmed some issues(eg. 90920、89396、90849、90923、90928、91065、91146). but I don't know whether the test results I have reported are clear enough and easy for others to understand.So please have a look when not busy and give me some advice.Thanks.
Your issue entries are moderately easy to understand, and have the required detail. (I have checked them, and officially confirmed or added information to them.)
I suggest starting each entry with your build and system details, e.g. "DEV300_m21_en WinXP:". This is the first piece of information we need.
Numbered lists (1, 2, 3) are used in issues to describe steps followed, so please use alphabetical lists (a, b, c) for other descriptions, e.g.
(a) find（all) and replace (all) are greyed-out till something is written in the 'search for' box.
Please leave one space after each closing punctuation mark or word (not after opening brackets or quotation marks). Use capital letters (and possibly quotation marks) for names of menu items etc., e.g
"Find All" Find All You don't need to use a punctuation mark to separate list items: (a) item A (b) item Balthough you should always complete a full sentence with a full stop (.), or question mark if it is a question.
You don't need to use any introductory or final-greeting expressions (e.g. "Frankly.") when adding information to issues. The person reporting the issue may end with "Thanks" or some other way of expressing appreciation for our efforts, but the format of issue information is simply adding data. It is not a personal communication. (I know this feels uncomfortable for you, but just think of it as a code routine.)
You can request additional information from the user who has reported the issue. Often, users forget to tell us which build or system they are using. You can also ask them to test the problem in the newest build, if it was reported more than a week or two ago.
Issue 91065 has been marked as a duplicate of issue 6087, which has been fixed in cws_odff04 and will be integrated into the 3.0 codeline. It's not always easy to find duplicates, because people report the same problem in different ways: sometimes very different ways! But it's a good idea to be aware that duplicates may exist. Compare similar issues.
When you add information to an issue, please don't use any language other than English. It is important that other people can read the issues.
"validating only on Windows XP(只在Windows Xp中进行了验证)"You don't need to add all this, just the version number etc. first, as I showed above. Only use "validating" in this way when you have been able to confirm the issue. Although validation is a process, using it as a classification comment like this gives the impression that you have confirmed the issue. In the case of issue 91146, you were unable to open the text document, and actually performed the issue tasks without the problem mentioned. Please attach your Excel document with nested formulae, so others can compare it with the user's attachment.
It is a big help that you test and confirm issues like this. Please keep doing it! :)
from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n
PGP.sig
Description: This is a digitally signed message part
