ConText: Text overflow over into the footer











up vote
0
down vote

favorite












In the MWE the text overflows into the footerdistance and into the footer. Why is this happening and how can I avoid it? The documents are generated and very long.



The split at placetable seems to be the cause for the overflow. Is there a other way to split tables over multiple pages?



updated MWE:



setupexternalfigures[location={local,global,default}]





showframe



starttext





externalfigure[cow][scale=600]



emptylines[26]





placetable[here,split]

   

   {}  {

startxtable

  startxtablehead

    startxrow

      startxcell text  stopxcell

    stopxrow

  stopxtablehead

  startxtablebody

    startxrow

      startxcell text stopxcell

    stopxrow

  stopxtablebody

stopxtable

}

Text



overflowing text into the footer, overflowing text into the footer



stoptext





context







share|improve this question




















  • 2




    If you want more control over the layout use definemeasure to set the values but don’t use topspace etc. to set the main values for the layout. The first big problem in your document is the missing brace for the first float, another is the split option because the float can’t be splitted. To create dummy lines you can use the emptylines[<NUMBER>] command.
    – Wolfgang Schuster
    17 hours ago










  • The first brace is wrong. I must have overlooked it when creating the mwe. The split is necessary, otherwise the table cannot be split over multiple pages. I minified the mwe further. The split attribute seems to play a big role.
    – Christopher Bock
    5 hours ago










  • can you provide a complete MWE that compiles and produces the undesired result?
    – FLonLon
    4 hours ago















up vote
0
down vote

favorite












In the MWE the text overflows into the footerdistance and into the footer. Why is this happening and how can I avoid it? The documents are generated and very long.



The split at placetable seems to be the cause for the overflow. Is there a other way to split tables over multiple pages?



updated MWE:



setupexternalfigures[location={local,global,default}]





showframe



starttext





externalfigure[cow][scale=600]



emptylines[26]





placetable[here,split]

   

   {}  {

startxtable

  startxtablehead

    startxrow

      startxcell text  stopxcell

    stopxrow

  stopxtablehead

  startxtablebody

    startxrow

      startxcell text stopxcell

    stopxrow

  stopxtablebody

stopxtable

}

Text



overflowing text into the footer, overflowing text into the footer



stoptext





context







share|improve this question




















  • 2




    If you want more control over the layout use definemeasure to set the values but don’t use topspace etc. to set the main values for the layout. The first big problem in your document is the missing brace for the first float, another is the split option because the float can’t be splitted. To create dummy lines you can use the emptylines[<NUMBER>] command.
    – Wolfgang Schuster
    17 hours ago










  • The first brace is wrong. I must have overlooked it when creating the mwe. The split is necessary, otherwise the table cannot be split over multiple pages. I minified the mwe further. The split attribute seems to play a big role.
    – Christopher Bock
    5 hours ago










  • can you provide a complete MWE that compiles and produces the undesired result?
    – FLonLon
    4 hours ago













up vote
0
down vote

favorite









up vote
0
down vote

favorite











In the MWE the text overflows into the footerdistance and into the footer. Why is this happening and how can I avoid it? The documents are generated and very long.



The split at placetable seems to be the cause for the overflow. Is there a other way to split tables over multiple pages?



updated MWE:



setupexternalfigures[location={local,global,default}]





showframe



starttext





externalfigure[cow][scale=600]



emptylines[26]





placetable[here,split]

   

   {}  {

startxtable

  startxtablehead

    startxrow

      startxcell text  stopxcell

    stopxrow

  stopxtablehead

  startxtablebody

    startxrow

      startxcell text stopxcell

    stopxrow

  stopxtablebody

stopxtable

}

Text



overflowing text into the footer, overflowing text into the footer



stoptext





context







share|improve this question















In the MWE the text overflows into the footerdistance and into the footer. Why is this happening and how can I avoid it? The documents are generated and very long.



The split at placetable seems to be the cause for the overflow. Is there a other way to split tables over multiple pages?



updated MWE:



setupexternalfigures[location={local,global,default}]





showframe



starttext





externalfigure[cow][scale=600]



emptylines[26]





placetable[here,split]

   

   {}  {

startxtable

  startxtablehead

    startxrow

      startxcell text  stopxcell

    stopxrow

  stopxtablehead

  startxtablebody

    startxrow

      startxcell text stopxcell

    stopxrow

  stopxtablebody

stopxtable

}

Text



overflowing text into the footer, overflowing text into the footer



stoptext





context




context






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 5 hours ago

























asked 21 hours ago









Christopher Bock

505




505








  • 2




    If you want more control over the layout use definemeasure to set the values but don’t use topspace etc. to set the main values for the layout. The first big problem in your document is the missing brace for the first float, another is the split option because the float can’t be splitted. To create dummy lines you can use the emptylines[<NUMBER>] command.
    – Wolfgang Schuster
    17 hours ago










  • The first brace is wrong. I must have overlooked it when creating the mwe. The split is necessary, otherwise the table cannot be split over multiple pages. I minified the mwe further. The split attribute seems to play a big role.
    – Christopher Bock
    5 hours ago










  • can you provide a complete MWE that compiles and produces the undesired result?
    – FLonLon
    4 hours ago














  • 2




    If you want more control over the layout use definemeasure to set the values but don’t use topspace etc. to set the main values for the layout. The first big problem in your document is the missing brace for the first float, another is the split option because the float can’t be splitted. To create dummy lines you can use the emptylines[<NUMBER>] command.
    – Wolfgang Schuster
    17 hours ago










  • The first brace is wrong. I must have overlooked it when creating the mwe. The split is necessary, otherwise the table cannot be split over multiple pages. I minified the mwe further. The split attribute seems to play a big role.
    – Christopher Bock
    5 hours ago










  • can you provide a complete MWE that compiles and produces the undesired result?
    – FLonLon
    4 hours ago








2




2




If you want more control over the layout use definemeasure to set the values but don’t use topspace etc. to set the main values for the layout. The first big problem in your document is the missing brace for the first float, another is the split option because the float can’t be splitted. To create dummy lines you can use the emptylines[<NUMBER>] command.
– Wolfgang Schuster
17 hours ago




If you want more control over the layout use definemeasure to set the values but don’t use topspace etc. to set the main values for the layout. The first big problem in your document is the missing brace for the first float, another is the split option because the float can’t be splitted. To create dummy lines you can use the emptylines[<NUMBER>] command.
– Wolfgang Schuster
17 hours ago












The first brace is wrong. I must have overlooked it when creating the mwe. The split is necessary, otherwise the table cannot be split over multiple pages. I minified the mwe further. The split attribute seems to play a big role.
– Christopher Bock
5 hours ago




The first brace is wrong. I must have overlooked it when creating the mwe. The split is necessary, otherwise the table cannot be split over multiple pages. I minified the mwe further. The split attribute seems to play a big role.
– Christopher Bock
5 hours ago












can you provide a complete MWE that compiles and produces the undesired result?
– FLonLon
4 hours ago




can you provide a complete MWE that compiles and produces the undesired result?
– FLonLon
4 hours ago















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f460142%2fcontext-text-overflow-over-into-the-footer%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f460142%2fcontext-text-overflow-over-into-the-footer%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

サソリ

Image
この記事は検証可能な参考文献や出典が全く示されていないか、不十分です。 出典を追加して記事の信頼性向上にご協力ください。 （ 2019年1月 ） 「 サソリ 」のその他の用法については「サソリ (曖昧さ回避)」をご覧ください。 「 スコーピオン 」と「 スコルピオン 」はこの項目へ転送されています。その他の用法については「スコーピオン」をご覧ください。 サソリ目 生息年代: 430–0 Ma PreЄ Є O S D C P T J K Pg N シルル紀前期-現世 ダイオウサソリ（ Pandinus Imperator ） 分類 界 : 動物界 Animalia 門 : 節足動物門 Arthropoda 亜門 : 鋏角亜門 Chelicerata 綱 : クモガタ綱 Arachnida 目 : サソリ目 Scorpiones 学名 Scorpiones C. L. Koch, 1837 英名 Scorpion 上科 Pseudochactoidea キョクトウサソリ上科 Buthoidea Chaeriloidea Chactoidea Iuroidea Scorpionoidea サソリ （ サソリ類 、 蠍 、 蝎 、 scorpion ）は、鋏角亜門・クモガタ綱の サソリ目 （ Scorpiones ）に属する節足動物の総称である。体の前端に鋏型の触肢、後端に毒針を有する捕食者である。 1700種以上を含め、最古の化石記録は4億3千万年前のシルル紀まで遡る。有毒生物として広く知られるが、人間の命にかかわる毒を持つものはごく一部の種類に過ぎない。 目次 1 形態 1.1 前体 1.2 後体 1.2.1 中体 1.2.2 終体 2 雌雄 3 生態 3.1 天敵 3.2 生殖 4 分布 5 毒 6 蛍光現象 7 分類
Read more

広島県道265号伴広島線

Image
一般県道 広島県道265号伴広島線 路線延長 km 起点 広島県広島市安佐南区伴東7丁目 終点 広島県広島市中区榎町 接続する 主な道路 （記法） 広島県道38号広島豊平線 広島県道71号広島湯来線 山陽自動車道五日市IC 国道183号（ 国道261号重複） ■テンプレート（■ノート ■使い方） ■PJ道路 広島県道265号伴広島線 （ひろしまけんどう265ごう ともひろしません）は広島県広島市安佐南区から広島県広島市中区を結ぶ一般県道である。 目次 1 路線データ 2 通過する自治体 3 見どころ 4 接続道路 4.1 本線 4.2 旧道 5 別名 6 関連項目 路線データ 本線 起点：広島市安佐南区伴東7丁目・大原下橋南詰交差点（広島県道38号広島豊平線（本線・旧道）交点） 終点：広島市中区榎町・十日市交差点（国道183号（国道261号重用）交点） 総延長： 旧道 起点：広島市安佐南区伴東4丁目・新細坂交差点（広島県道38号広島豊平線交点） 終点：広島市安佐南区伴中央4丁目・寺組橋(南)交差点（広島県道265号伴広島線（本線）交点） 総延長： 通過する自治体 広島県 広島市（安佐南区、佐伯区、西区、中区） 見どころ 広島高速交通広島新交通1号線（アストラムライン） 広島広域公園 広島広域公園陸上競技場（広島ビッグアーチ） 己斐峠 己斐橋（太田川放水路） 天満橋（天満川） 接続道路 本線 広島県道38号広島豊平線（本線・旧道）（広島市安佐南区伴東7丁目・大原下橋南詰交差点〔起点〕） 広島県道71号広島湯来線（本線）（広島市安佐南区伴中央2丁目・伴交番入口交差点 - 広島市安佐南区伴中央4丁目・寺組橋(南)交差点間で重用） 広島県道71号広島湯来線（旧道）（広島県道265号伴広島線（旧道）重用）（広島市安佐南区伴中央4丁目・寺組橋(南)交差点） 広島県道71号広島湯来線（広島市安佐南区伴中央4丁目・寺組橋(南)交差点 - 広島市佐伯区五日市町石内・五月が丘(南)交差点間で重用）
Read more

Accessing regular linux commands in Huawei's Dopra Linux

Image
4 Backstory: I have a Huawei HG8245 router in my house and I want to change the default username/password. I've tried following this guide but the config file always gets reset. My ISP isn't helping either so I'm looking for other ways to accomplish this. The router has telnet access so this seems like a way to change the credentials. The first shell I gain access to looks like this: WAP> Pressing "?" gives me a list of available commands which I've pasted here, the two interesting ones are "su" and "shell". I can't seem to get su access, even after logging in as root (challenge password prompt, and then nothing happens), but shell gives me a proper linux shell. WAP>shell BusyBox v1.18.4 (2017-12-26 17:06:34 CST) built-in shell (ash) Enter 'hel
Read more