In my case, I use TexMaker in the drafting stage at which the structure and writing change a lot and then switch to Visual Code in the review stage at which usually grammar checking is needed. Unfortunately, sometimes you need all of these features as me. Furthermore, if your documents are large and have complicated structure, Visual Code would not be a good environment for you. On the other hand, if your writing has a lot of symbols such as mathematic formulas and you are not familiar with the latex symbols, TexMaker will make the things easier for you. So that, if you need help on the grammar check, Visual code should be a better choice. TexMaker does not support grammar checking and auto build on save while Latex Workshop does not support symbol input assistance and outline of nested documents. On contrast, Visual Studio Code as a general code editor is more flexible and extensible. As a dedicated latex editor, TexMaker is a self-contained tool with all the built-in feature. Result Requirementįrom the comparison result we can see that both TexMaker and Latex Workshop support most of my requirement. The detail information of the configuration or extension are depicted for reference. Some requirements depend on configuration or extension. The comparison was applied to both Windows and Mac OX S. So the comparison has limitation and might not be a suitable reference for your case. The comparison is in the dimensions of my requirements. But I would like to start with this comparison and might extend it later. There are some other options as Latex editor. However, I never think about writing Latex with Visual Code until someone told me that might be a better option. I have been used TexMaker for Latex file editing and Visual Code for editing my personal website for about a year when I am writing this blog. The obsolete OS X 32-bit version is no longer provided (the 4.Compare Texmaker and LaTex Workshop(An add-on of Visual Studio Code)īased on my own requirements, I compared TexMaker and LaTex Workshop.The OS X Lion/Moutain/Maverick is now compiled with Qt 5.3.2 and poppler 0.26.The windows versions are now compiled with poppler 0.26.A bad behavior when spelling the document while a text is selected has been fixed (issue 1393).The xelatex command is now included in the "Tools" menu.A bug related to some shorctuts (ctrl+shift+?) has been fixed.A crash if the "% !TEX encoding=" meta tag is not valid has been fixed.spx extensions have been added to the "Clean" command (users requests) - cs, de, el, hu, pl, ru, se and vi translations have been updated (thanks to all the translators) Support for the meta tags "% !TEX encoding=" and "% !TEX spellcheck" has been added (the meta tag "% !TEX root" is already supported).The list of furnished scripts is displayed in the "Run Script" sub-menu of the "User" menu (if a script is located at the same place than the furnished scripts, it will appear automtically in this menu). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |