If you have a master document which uses \includepackage[ngerman]{babel} and then \input{}s other documents and these included documents use umlauts transcribed as "a, "o, etc., then the words with umlauts are initially marked as spell errors, even if your master is correctly declared as master. If you write \includepackage on the top of the included document, suddenly the red marks disappear and the spell check works from now on. See attachment. You can now delete the \includepackage statement again and it continues working. Reproduced with 2.8.8 on Debian.
master.tex:
\documentclass{scrartcl}
\usepackage[ngerman]{babel}
\begin{document}
\input{include}
\end{document}
fixed in repository
I still have the issue in 2.9.5 hg 5364+:217ed424dd0b+
I can't reproduce a problem. Step-by-step guide ?
I can reproduce it with existing files master.tex and include.tex
1)
2)
Both times, include.tex is opened as in attachment #1 where ungl"ucklicherweise is marked as error. In contrary, umlauts in master.tex are correctly handled.
I am at hg branch default commit 5364:217ed424dd0b without local modification of the source code. In particular, the "%replace" category which you introduced in your commit 4907:7fa24b36f700 to fix the issue is present.
master.tex:
\documentclass{scrartcl}
\usepackage[ngerman]{babel}
\begin{document}
\input{include}
Dieser Text ist "uber und "uber voll mit Umlauten.
\end{document}
include.tex:
Dieser Satz hat ungl"ucklicherweise Umlaute, sodass es manchmal Fehler gibt.
Last edit: Klaus Schneider-Zapp 2015-08-15
fixed
Thanks for the fix.
For me it is now half-fixed: After launching with a lengthly text, in the first part of the text the special characters are correctly recognised while further on they are still treated as an spell error. As before, writing
\usepackage
in a single line at the top fixes all spell issues. However, after your change also editing the master document does the same.
I could not yet find out find a systematic when some parts are correctly recognised at startup or not. My test text still does not work.
well, I don't see a bug here anymore ...
I have removed my configuration and recompiled everything from scratch and now it is working. Thanks again.