Add a comment back to the submitter thanking them for the bug report and asking for some further information. Tell them about recent fixes that have been implemented regarding UTF8 and that it may be fixed but we're not sure. Ask if he would mind downloading a recent snapshot and seeing if he still has the problem. Also ask if anyone else has seen the same problem.
If we do not hear back from him or someone else within a week or so, then go ahead and close the bug either as Fixed, if you feel you probably got it fixed, or Works For Me. In either case, encourage them to resubmit the bug with additional details if they still encounter it in the future, and give a pointer to the Reporting Bugs page.
You may want to use this same approach for all UTF8-related bugs that have been reported. This would be a good time for all those submitters to recheck their bugs against the nightlies.
Bryce
On Tue, 1 Feb 2005, Jon A. Cruz wrote:
Given that bug 1079194 is a bit ambiguous, and that there's ongoing effort for other bugs that may have alread fixed this, I'm thinking of bumping it over to pending.
Sound reasonable?
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel