Re: etags test is broken on MS-Windows

[Eli Zaretskii <eliz@gnu.org>]

> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: pot@gnu.org,  eggert@cs.ucla.edu,  emacs-devel@gnu.org
> Date: Fri, 22 May 2015 21:50:48 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Or maybe you mean the use case where a Latin-1 file is read into an
> > Emacs buffer, and each non-ASCII character is expanded into a UTF-8
> > sequence.  Indeed, that will make the byte counts inaccurate (and
> > etags.el will have to compensate by searching around the specified
> > place).  One more reason not to change anything, I guess.
> 
> ??? It's exactly the counter argument.  The indices in the tag file must
> be file offsets, everything else will lead to wrong offsets.

If by "file offsets" you mean counting bytes in the file, then those
will also be wrong after decoding non-ASCII characters, unless the
file was encoded in UTF-8 to begin with, right?

And if you mean counting characters in the file, then etags will be
unable to do that, unless it grows the capability to detect the
encoding of the file, or rely on the locale and assume that the file
is encoded in locale's codeset.  Right?

Or am I again missing something?