There are many packages out there that do pretty much the same. However, there are also usually many settings and tweaks needed to get it to look just right. This package saves you from all this hassle — just include it and you're done. I originally wrote this package for myself to have colourful source code highlighted in LaTeX, looking exactly like in the Matlab editor — being able to just copy-paste the code directly (no pre-treatment with highlight.m or the likes), or simply give a file name and have its contents included and syntax highlighted. Again, this packages relies on a bunch of other packages (and in particular the listings package for the actual work), but spares you from loads of configurations. So please first check the source code or the configuration options of the packages used if you have any issues. I've also thrown together a small demo-document (now included) which should give you a quick example on how to actually use the package.

Hi Florian, I am using Lyx, and got an error message in the text below, when I tried to show the following one-line.m code: fprintf ( 1, ' Hello, world! N' ); In the error message, it shows that LaTex Error: Command textquotesingle unavailable in encoding T1. And the corresponding description shows more detail as follows: 'fprintf ( 1, ' Hello, world!

N' ); Your command was ignored. Type I to replace it with another command, or to continue without it.' Do you have any idea of what is going on? Fantastic latex module. I have one issue with the syntax highlighting though; when I clear a variable with the code clear varname in Maltab, the variables are in purple.

I thought that this might be the package not understanding the method of passing variables in the form of function 'charvariable' matrixvariable as opposed to function('charvariable',matrixvariable) but when I write the code load 'data.m' It formats the 'data.m' in purple as I would expect. Maybe it's just something curious about the clear keyword. Great package though! @ Ken H — thanks for your positive comment. I've had a look at your problem, but I can't reproduce it.

Using my demo document (see link at the top), leaving mathescape=false as set by default in the document and including the tipa package, I can simply type § textpipe§ to get the pipe showing up just fine. Not sure why this is not working for you. Try with the demo document, as this is a very barebones document. If it works there, but doesn't with your document, then it's almost sureley some package clash.

Updated the demo document. @ Rasmus: I've shuffeled things around a little bit in the source code, and added a description to make it really clear how to change the font size. @ turker: I've modified the 'solution' to the end/end problem; you can now use 'iend' in the source code to get 'end' typeset in black (when used to reference the last element in vector.) @ All: If you use the LaTeX escape functionality in comments, there's now an easy way of getting that typeset in the same style as the rest of the comment, see the demo document. @ Lagrange: I've used the package in the appendix many times and it works fine. I suspect (because of the upquote error message) that you have a slightly outdated version of the listings package installed. Make sure you have the latest version. @ Daniel: I know, I know, I'd love to have this fixed too, but such functionality appears to be quite unique to the Matlab scripting language, and the listings package (which does all the work) does not support such behaviour.

Package Latin1 Latex Download For Mac Pc

I've mailed the package maintainer already, but he never got back to me. @ Alvin: Sorry, I never got the error you have. But thanks for pointing out a work-around, for those that do not have a 'proper' TeX installation, including all fonts and map-files. You're right, the 'textcomp' package is only there for the upquotes.

The idea of using that comes straight from the listings documentention (Section 4.7). @ turker: Thank you very much for sharing your work-around for the 'end'-issue. While it's not too sleek, it works very well! Unfortunately there's little I can do to fix this in a more elegant way. As I said many times, the actual work is done by the listings pacakge, and as far as I can see it doesn't support different colouring of the same keyword.

I'm of the idea that, whenever possible, you should stick to utf8 (unicode) as it is finally the solution about character encodings on computer documents. Of course you only have to make sure that your text editor supports and behaves nicely with unicode documents. In either case, if you have to work with collaborators, you have to make sure that they do also use decent text editors that can handle the appropriate encoding without messing with the special characters. For documents with many collaborators I've learned the hard way that it is better to stick to ascii and use (La)TeX commands to produce special characters.

In short:. utf8 supports much more characters than latin1. utf8 is multilingual and cross-platform spread, latin1 is mainly used on Windows.

Unicode, which is supported by utf8, is international standard and it shall support all languages and shall handle all kinds of writing. Utf8 is the widest spread encoding for Unicode and it is backwards-compatible with ASCII (in contrary to other Unicode encodings).

In utf8, each character is represented by 1 to 4 bytes. That's why the number of possible symbols is really huge.

Latin1 uses just one byte, beeing limited to a maximum of 256 characters. I think it uses just 191 of 256 possible. So, utf8 might be already be favourable if you use just one platform. Utf8 is the standard encoding on Linux and Mac OS X.

The number of LaTeX editors supporting utf8 on Windows increased, for instance TeXworks uses it by default. If there's a possibility that anybody, including you, would open your document on a Mac or on Linux, I recommend to use utf8.

Package Latin1 Latex Download For Mac Mac

This already concerns german umlauts. The background. Pure ascii is a 7-bit encoding that is only good for english, the german characters is missing. Latin1 is a 8-bit (1 byte) character encoding that used to be the standard encoding in Germany some 5-10 years ago. And it does support the special german characters. If you have a look at the you quickly realised that it was a little bit messy but it did work.

So to solve this in a nicer way, utf8 was created and since it is using 1-4 bytes to store one character. More or less all special characters from all different countries inclusive the Asian ones can be saved in the same character encoding.

And since all modern OS (Windows, Linux and MacOS) use utf8, you are probably using it right now without even knowing it.