DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23647>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23647 when build fails due to character-encoding problems, no linenumber is given ------- Additional Comments From [EMAIL PROTECTED] 2003-10-07 22:53 ------- Thanks for replying that fast. (4 Instances in 10 hours). I received this answer: --- answer--- There is no possibility to reliably report a line number in case of a problem with the encoding. After all, the bytes mapped onto LF may be in error too. --- eoa --- This sounds reasonable. But I encountered this error sometimes, and everytime it occured, other linenumbers were accurat. Differences between MAC-OS, LINUX and WinDos would lead to following possibilities: A calculated linenumber of 20 could mean the error is in line 20, in line 10 or in line 40. If I get a wrong linenumber, I could force an error, and find out the relationship between mentioned line number and real line number. But probably the linenumber is correct. So a linenumber which is accurat most of the times and only in very few times wrong would be more helpful, than no linenumber, which forces me to guess. On the other side: Perhaps I will not run into the user-error of wrong encoding again, after finding out, that I have to specify 'iso-8859-1' encoding. Let other users search their files by guessing too. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
