You are not telling us which version of TexnicCenter you are using.
I advise you to do as every Wind0ws user often does. Uninstall the program, reboot your system and install texniccenter again. Be aware, that TXC 2.0 is stable and should be used without hesitating over version 1.0
If the problem persists, try to open the program via the terminal, i hope there will be some useful information. The maintainer would be greateful for feedback: Texniccenter support.
Statistics: Posted by Johannes_B — Mon Dec 09, 2013 4:25 pm
I encountered a huge problem with TexnicCenter. To make it short: It’s not working AT ALL.
When I try to create a new empty project TexcnicCenter simply shuts down without ANY error message whatsoever. When I name my empty project “Test” the only files that get created before the program shuts down are:
Not sure if this is all that’s supposed to be created for an empty project. Nontheless, the major problem is the program simply shutting down.
I can’t even open existing .tex files (created with an older TexnicCenter version). The same happens.
My OS is Win7 64 Bit. I tried both the 32bit and the 64bit MikTex distribution and installed them in C:\MikTex.
Not sure what’s going on here. Google was not help either.
I would really appreciate any help!
Thanks a lot!
Statistics: Posted by ConSeannery — Mon Dec 09, 2013 1:31 pm
I upgraded TeXnicCenter (TXC) from a very old version to the current stable version (2.02). Everything works fine except that I get the following error message when I start the program.
The language file for the selected language is not compatible with this version of TeXnicCenter. The default language (English) will be used instead.
I’d like to use the German version.
I’d appreciate it if someone could point me in the right direction how to get rid of this message.
Statistics: Posted by mpwyn — Wed Dec 04, 2013 1:02 pm
Once again. The Ad0be Reader is not recommendable when editing LaTeX documents because it is uncomfortable regarding forward and inverse search between source code and PDF output. It does not support SyncTeX and therefore is only usable for viewing (and perhaps printing) the finalized document. The developers of TeXnicCenter (TXC) have decided for good reasons to make Sumatra PDF the standard viewer.
Statistics: Posted by localghost — Thu Nov 21, 2013 9:16 pm
Thank you Bruno! I changed A10 to A11, and things started working for me.
Statistics: Posted by Catherine Liao — Thu Nov 21, 2013 9:00 pm
When I unzip the attached code to write an article in TeXworks, it compiles fine and presents to me the PDF output without any problem (pdfLaTeX compile option).
But, doing the same procedure in TeXnicCenter, the error messages in the PNG attached file are presented (it is not generated the .log file).
Does anyone know what is happening?
Statistics: Posted by Jaraqui — Mon Nov 18, 2013 11:12 pm
Thanks for the answers. I use TeXnicCenter 2.02 stable 64 bit.
Statistics: Posted by krintel — Mon Nov 11, 2013 10:50 am
This is a small, niggling kind of problem, but I thought I’d put it up in case anyone smarter than me has a simple solution.
In TeXnicCenter (I’m running the latest version, currently 2.02 stable), when you are browsing the list of warnings and errors in a compiled document, sometimes an error will call up a different file that has been included somehow. This is very useful when there’s an error coming from your bbl file, much less so when there’s a persistent warning in a cls file that I have to use from my employer, which I can’t edit. Then it’s annoying to have to close the new file every time.
So I’m wondering if there’s a good way to prevent TeXnicCenter from pulling up additional files than the one open. I imagine I might need some sort of workaround that cripples its ability to open files. I played around with the commands it uses to call up Windows Explorer (in Tools -> Customize -> Tools) but couldn’t figure anything out.
Thanks in advance for any help you can give!
Statistics: Posted by natty — Sun Nov 10, 2013 1:29 am
You can also choose the encoding while saving as within TXC. Choose utf8 without BOM. A notification to the maintainers would be great though.
Statistics: Posted by Johannes_B — Tue Nov 05, 2013 9:59 am
I am using TeXnicCenter (TXC) 2.0 Beta 2 (32bit).
I was creating a new command for
\input of .tex files including other functionality as followed:
- Code: • Open in writeLaTeX
% Command for including a finding into the report
Normally if I use
\input I see all my files in the data tree from of the Explorer Tool, so that I am able to click directly on the file I want to edit. But with this new command, this feature of
\input doesn’t work anymore. So I always have to open the explorer in an own window a pull the files into TXC.
I know that this is just a short code snippet I provided, tell me if you need more
Statistics: Posted by LaTeXer — Mon Nov 04, 2013 5:00 pm