I'm facing compiling problems after the TM update to 1.5.8 (bleeding edge). I save my tex-files in my project in Latin1. As soon as i open a new file in the project and want to compile it, i get the following error message. "LaTeX Error: Command \textcurrency unavailable in encoding T1" When i save the file with "save as" and make sure TM saves it in latin1, and i close the file, then the compile process suceeds. I'm sure I haven't faced this problem with 1.5.7. When i downgrade to this version, everything works fine. as soon as i upgrade, i have this problem. I think TM wants to save everything in utf8. At least i realised that former latin1 docs were saved as utf8. In the prefs pane > advanced> saving there is "latin1" listed under "file encoding".
Hope somebody can help me
I've got an idea that this is probably related to a change in how the current document is saved before latex is run. Alex/Allan.... Does TextMate.save_current_document ignore the TM preference for what encoding to use when saving a file? I can't find any evidence in the source that it is checking for a specific encoding preference but I'm not too familiar with that code.
Brad
On Mon, Dec 8, 2008 at 11:26 AM, macvuk@gmail.com macvuk@googlemail.comwrote:
I'm facing compiling problems after the TM update to 1.5.8 (bleeding edge).I save my tex-files in my project in Latin1. As soon as i open a new file in the project and want to compile it, i get the following error message. "LaTeX Error: Command \textcurrency unavailable in encoding T1" When i save the file with "save as" and make sure TM saves it in latin1, and i close the file, then the compile process suceeds. I'm sure I haven't faced this problem with 1.5.7. When i downgrade to this version, everything works fine. as soon as i upgrade, i have this problem. I think TM wants to save everything in utf8. At least i realised that former latin1 docs were saved as utf8. In the prefs pane > advanced> saving there is "latin1" listed under "file encoding".
Hope somebody can help me
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Am 09.12.2008 um 02:57 schrieb Brad Miller:
I've got an idea that this is probably related to a change in how the current document is saved before latex is run.
Alex/Allan.... Does TextMate.save_current_document ignore the TM preference for what encoding to use when saving a file? I can't find any evidence in the source that it is checking for a specific encoding preference but I'm not too familiar with that code.
Brad
An evidence for your idea is that my project consists of more than 20 files, and if there would be a general coding problem, than the error should occur in every of these documents. But the error is only related to the master document and to the document that is open AND in which i start the typesetting command. I have to close all documents of my project after saving with "save as" in latin1 and replace the old one.
For typesetting, I have a document with only one letter in my project, which is not included in my Master file. But without this, it would not be possible to run "CMD-R".
-- Brad Miller Assistant Professor, Computer Science Luther College
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Dec 8, 2008, at 11:48 PM, macvuk@gmail.com wrote:
Am 09.12.2008 um 02:57 schrieb Brad Miller:
I've got an idea that this is probably related to a change in how the current document is saved before latex is run.
Alex/Allan.... Does TextMate.save_current_document ignore the TM preference for what encoding to use when saving a file? I can't find any evidence in the source that it is checking for a specific encoding preference but I'm not too familiar with that code.
Brad
An evidence for your idea is that my project consists of more than 20 files, and if there would be a general coding problem, than the error should occur in every of these documents. But the error is only related to the master document and to the document that is open AND in which i start the typesetting command. I have to close all documents of my project after saving with "save as" in latin1 and replace the old one.
For typesetting, I have a document with only one letter in my project, which is not included in my Master file. But without this, it would not be possible to run "CMD-R".
I think the problem is in fact related to TextMate.save_current_document. I will look into it.
—Alex
Thanks Alex. macvuk.. It looks like Alex has reverted the change to the LaTeX bundle that was causing your problem. If you update your latex bundle to the latest version in the subversion repository your problem should be solved.
Brad
On Tue, Dec 9, 2008 at 2:13 AM, Alex Ross tm-alex@rosiba.com wrote:
On Dec 8, 2008, at 11:48 PM, macvuk@gmail.com wrote:
Am 09.12.2008 um 02:57 schrieb Brad Miller:
I've got an idea that this is probably related to a change in how the current document is saved before latex is run.
Alex/Allan.... Does TextMate.save_current_document ignore the TM preference for what encoding to use when saving a file? I can't find any evidence in the source that it is checking for a specific encoding preference but I'm not too familiar with that code.
Brad
An evidence for your idea is that my project consists of more than 20 files, and if there would be a general coding problem, than the error should occur in every of these documents. But the error is only related to the master document and to the document that is open AND in which i start the typesetting command. I have to close all documents of my project after saving with "save as" in latin1 and replace the old one.
For typesetting, I have a document with only one letter in my project, which is not included in my Master file. But without this, it would not be possible to run "CMD-R".
I think the problem is in fact related to TextMate.save_current_document. I will look into it.
—Alex
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Dec 9, 2008, at 6:28 PM, Brad Miller wrote:
macvuk.. It looks like Alex has reverted the change to the LaTeX bundle that was causing your problem. If you update your latex bundle to the latest version in the subversion repository your problem should be solved.
Though you really should use UTF-8 if at all possible!
—Alex
Thanks Alex and Brad, after updating the Latex Bundle (Revision 10994, is this correct?), everything works fine again.
@Alex: is there an easy way to "convert" all the files in my project into utf8? Or do I have to open every single file and make the "save as" command, choosing "utf8"?
Am 10.12.2008 um 03:28 schrieb Brad Miller:
Thanks Alex.
macvuk.. It looks like Alex has reverted the change to the LaTeX bundle that was causing your problem. If you update your latex bundle to the latest version in the subversion repository your problem should be solved.
Brad
On Tue, Dec 9, 2008 at 2:13 AM, Alex Ross tm-alex@rosiba.com wrote: On Dec 8, 2008, at 11:48 PM, macvuk@gmail.com wrote:
Am 09.12.2008 um 02:57 schrieb Brad Miller:
I've got an idea that this is probably related to a change in how the current document is saved before latex is run.
Alex/Allan.... Does TextMate.save_current_document ignore the TM preference for what encoding to use when saving a file? I can't find any evidence in the source that it is checking for a specific encoding preference but I'm not too familiar with that code.
Brad
An evidence for your idea is that my project consists of more than
20
files, and if there would be a general coding problem, than the
error
should occur in every of these documents. But the error is only related to the master document and to the document that is open
AND in
which i start the typesetting command. I have to close all documents of my project after saving with "save as" in latin1 and replace the old one.
For typesetting, I have a document with only one letter in my
project,
which is not included in my Master file. But without this, it would not be possible to run "CMD-R".
I think the problem is in fact related to TextMate.save_current_document. I will look into it.
—Alex
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-- Brad Miller Assistant Professor, Computer Science Luther College
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Dec 10, 2008, at 1:08 AM, macvuk@gmail.com wrote:
Thanks Alex and Brad, after updating the Latex Bundle (Revision 10994, is this correct?), everything works fine again.
@Alex: is there an easy way to "convert" all the files in my project into utf8? Or do I have to open every single file and make the "save as" command, choosing "utf8"?
You can use the iconv tool in Terminal. It doesn't seem to like “latin-1” as an encoding, so you may have to use the ISO number.
—Alex
-
Alex Ross -
Brad Miller -
macvuk＠gmail.com