Hi, thanks for your kind words: We are aware of the Unicode problem. The problem is, that the current editor component is totally based on non-unicode characters and this will make things hard to implement, but the problem is definitely on our todo list.
We also think about changing the editor component. Scintilla is a hot candidate and would also support unicode. We only will need to find someone with the time to integrate the new editor
Last edited by Sven on Tue Jan 16, 2007 12:13 pm, edited 1 time in total.
LaTeX Community Administrator
Originator of TeXnicCenter
I want to say as well that TeXnicCenter is a very good tool. I face the Unicode problem as well because I have to write my master thesis on an African language, it means I need input/output unicode support. I use Windows & MiKtex. Is there already an IDE like TeXnicCenter with unicode support? Or if not how to ''integrate'' an unicode supporting editor (which one?) with MiKtex? I would wait for TeXnicCenter to have the feature but I have to write my Thesis right now...
All the best,
Hi dear developers and users,
since I can't find any information elsewhere, I'll see whether we could get a news update here: is there any new status as to when the TNC editor will start supporting Unicode (UTF8). I suppose that presently the editor can't be configured to assume anything other than Windows 8-bit encoding. is this the case?
cheers
Gustav
Whats the progress here?
I am using kile here which does support any encoding you can think of - like utf-8.
I got many documents which i want to edit through texniccenter too - but the complete lack of utf-8 support is really a blocker.
Can anyone tell some release plan?
well, an interim solution that might work well for you might be to use an unicode-enabled 'feature-rich' text editor (personally, i use notepad++), set the encoding type to utf8 without BOM, and do the actual typing inthere.
While TeXnicCenter won't display the characters correctly, it should be able to save/process them, and since both programs ask to reload when they detect changes in the file by another program, this should work fairly well (since you won't be able to have save/edit conflicts)
zerospinboson wrote:well, an interim solution that might work well for you might be to use an unicode-enabled 'feature-rich' text editor (personally, i use notepad++), set the encoding type to utf8 without BOM, and do the actual typing in there.
Well probably everyone works around lack of Unicode support like that - but that's a nuisance too.. how often have you forgotten to switch back to your notepad++ or whatever and edited in TeXnic to realize that you messed up.
Lack of utf-8 support is a real blocker and I'm really sad to say that we had to remove TeXnic from our computer pools for that reason.
Last edited by ergodique on Mon Feb 11, 2008 3:13 pm, edited 1 time in total.
ergodique wrote:Well probably everyone works around lack of Unicode support like that - but that's a nuisance too.. how often have you forgotten to switch back to your notepad++ or whatever and edited in TeXnic to realize that you messed up.
actually, because both texniccenter and np++ tell you if the file has been changed by another program, the chance of that happening is very low
Last edited by zerospinboson on Wed Feb 20, 2008 4:07 am, edited 1 time in total.
