Hi Alex,
FWIW, I personally think that being able to provide IZ reports in one's
native language would still be the way to go, and that the IZ interface
still sucks big time for a "normal" user encountering a bug or a problem
with his version of OOo .
We had this discussion several times. Although it was a good way to
*file* an issue .. filing an issue is only the first step in a longer
process.
Filing an issue in your native language would break down the number of
people who can take care about it to a tenth or even lower number.
We had often the idea to provide an initial translation. But this would
not be of much help, as most of the issues need more feedback from the
initial reporter .. so .. we would need ongoing translation.
The only thing I can imagine is to keep an issue within the native
language of the reporter until it can be confirmed. then close this
issue, report a new one in english, what will become the "working" issue.
But even with this, there are some major problems:
- initial reporter cannot follow implementation and check, if his issue
becomes fixed.
- as long as the issue is in native language, it is not visible for
people not speaking this language (so you'll never know, if duplicates
exist)
- where would we get the ressources to keep the initial issue in ones'
native lang (this might work for larger native lang communities, but not
for minor ones)
Honestly speaking (and this might look not very userfriendly). As long
as we have 640 unconfirmed and 3500 new issues, it is not our problem to
get *more* issues reported. Our problem is to confirm them and make it
easier to developers to handle them.
If you are aware of users, willing to file issues but have troubles with
english, guide them to the native lang mailinglists. Often such issues,
are known, sometimes problms of wrong usage and could be easily handled
at a user list.
Of course, addressing both of these points potentially represents
significant problems for those who would have to deal with the reports
filed by users with little or no knowledge of the bug submission
process. At least with the interface as it currently stands, it is
fairly easy for QA to sort out the wheat from the chaff.
Regarding the interface, we had this discussion at [EMAIL PROTECTED]
http://native-lang.openoffice.org/servlets/BrowseList?list=dev&by=thread&from=535257
Main reason, why this didn't happen might be found in this mail:
http://native-lang.openoffice.org/servlets/ReadMsg?list=dev&msgNo=4074
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
