On 29. Jun 2007, at 19:39, Maxime Boissonneault wrote:
Ok, I was not really talking about modifying the code myself. I meant providing more information that you might need. [...]
The problem is that your source documents are scanned for completion candidates in their on-disk state.
The scanner cannot know what encoding you have used, and so it assumes (for good reason) UTF-8.
But in fact the stuff is malformed, when treated as UTF-8, so TM will discard it, when the label completion command tries to insert it.
So, as I have repeatedly written on this list; all TextMate commands which work on your files assume these files are UTF-8, UTF-8 is the only sane encoding to use, and supporting more is not only tedious, in many cases it is impossible.
The only improvements I plan in this department is more warnings when stuff is not UTF-8 ;)