很高興腳註在你那裡確實能斷行，這算是進步！噢，其實你是在單欄模式下，所以那可能是之前的修復... 你正在使用較新的版本嗎？（與此相關的最近腳註變更是在今年三月初修復的）。如果不是，請更新！
如果使用較新版本問題仍然存在，請繼續閱讀。
可能有幾種情況發生，而唯一能確定原因的方法是花大約半天時間閱讀大量晦澀的日誌文件，同時在旁邊打開原始碼...
不過，我可以猜測一下....
你會看到它包含了需要腳註的那一行，然後就停止了。所以... 出於某種原因，它在讀取腳註後決定，如果在該處分割腳註，頁面現在已經滿了。 它可以在兩個不同的地方做出這個決定：在讀取輸入時或在排版文字時。如果它在讀取輸入時做出了決定，那麼「排版文字」部分就沒有更多輸入可用，因此你會看到空白。
如果問題出在後半部分，那麼... 呃... 我可能在程式碼的某個地方算錯了數學。也可能是因為放置腳註後，出於其他原因，它決定頁面換行的理想位置就在其後。
我希望你的 ptxprint-mods.tex 檔案中沒有嘗試更改腳註行為的內容。如果有，請將它們註解掉。我也希望你敢於嘗試... 查看 Full view 的 "Advanced" 標籤頁，在右下角找到 "Show TeXpert hacks"：
然後前往打開的新標籤頁。那裡有一些控制項供你調整：
* "Enhanced paragraphed footnotes" 可能會有幫助，我不確定。這是一個「以舊方式處理」的相容性標誌，我記得它也會對非段落式腳註做一些微小變更。
* 降低 "Last note interline penalty" 會告訴程式碼允許在更多位置斷開腳註。（10000 應該意味著只在段落處斷開）。對於你這種正文與腳註的比例，你需要將其設為 500 左右。
* "Footnote factor single column" 也可以調整。將其設為 0 意味著在「讀取輸入」階段不會嘗試計算腳註大小。這可能會導致其他問題，但希望我們現在已經解決了那些問題。我實際上會建議將其設為 900 左右（假設它是 90%），這樣即使原始值出於歷史原因為 100（10%），它也會接近正確值...
* 最後注意：widowpenalty 和 Last note: clubpenalty 值 分別影響它認為在腳註段落最後一行之前斷行和在第一行之後斷行的嚴重程度。
* 各種 "split note" 數字希望是自明義的... 我不確定它們是否僅適用於段落式腳註。
如果這些都沒用，那麼將檔案壓縮發送給我就是最好的下一步。我無法承諾何時能抽出時間深入調查。
I'm just glad that footnotes are actually breaking for you, that's progress! Oh, actually, you're in single column mode, so that might have been an earlier fix... Are you running a recent version? (the last footnote changes relevant for this were fixed in early March this year). If not, please update!
If the problem is still there with a recent version, carry on reading.
So, there are several things that might be happening, and the only way to actually tell for certain is to spend about half a day reading lots of cryptic log files with the source code open beside you...
But, I can make a guess or 2....
You'll see that it is including the line needing the footnote, and then stops. So... for some reason it decided, having read the footnote, that the page was now full if it split the footnote where it did. It can make that decision in 2 different places: while reading the input or while laying up the text. If it made the decision while reading the input then there's no more input available to the 'laying up text' bit, and so you'll get gaps.
If the problem was in the second half, then... urm... I probably got some maths wrong somewhere in the code. It might also be that having placed the footnote, for some reason it decided that the ideal place to break the page was immediately after for some other reason.
I hope you don't have anything trying to alter footnote behaviour in your ptxprint-mods.tex file. If you do, please comment them out. I also hope that you're feeling brave... have a look at the Full view "Advanced" Tab, find "Show TeXpert hacks",on the bottom right:
and then go to the new tab that opens. Then there are some controls for you to play with:
* "Enhanced paragraphed footnotes" May help, I'm not sure. It's a "do things the old way" compatability flag, and I seem to remember it makes some minor changes to non-paragraphed footnotes too.
* Reducing the "Last note interline penalty" will tell the code that it's allowed to break the footnote in more places. (10000 should mean only break at paragraphs). For your sort of text-footnote ratio, you need it to be more like 500.
* "Footnote factor single column" could also be adjusted. Setting it to 0 will mean that it won't try to count footnote sizes at all during the "reading input" stage. That might cause other problems, but hopefully we've ironed those out by now. I'd actually try setting it to something like 900 (pretend it's 90%), so it's close to right, even though the original value is 100 (10%) for historical reasons...
* Last note: widowpenalty and Last note: clubpenalty values affect how bad it considers breaking before the last line and after first line of paragraphs in the footnote respectively.
* The various "split note" numbers are hopefully self explanatory... I'm not sure if they only apply to paragraphed notes or not.
If none of this helps, then sending me an archive is the best next step. I can't make promises about when I'll be able to dedicate the time to digging though.
機器翻譯自 English
