Merge “tabularx” and “longtable” with small patch instead of additional package just as for...











up vote
0
down vote

favorite












In this other question from 2012, a concise and functional solution has been suggested that merges tabulary and longtable into a new ltabulary.



Is there any way to adjust this patch to work for tabularx instead of tabulary as well?



Yes, for tabularx, there are ltablex and ltxtable. But if you don’t need extended features such as repeating headers, the minimal solution without an additional package, with reduced complexity, and with familiar syntax and usage is great to have, isn’t it?



Now simply replacing tabulary with tabularx in the patch does not work, as it has other constructs such as TY@final, endTY@final and TY@tabular that I don’t know the equivalent replacements for.



Perhaps one could find these in the source code for ltablex (about 99 lines apparently) or ltxtable (about 129 lines apparently).



If there are similarly concise replacements and the ported patch can be completed, it would be interesting to know how this can be done. On the other hand, it the patch requires more code for tabularx than for tabulary, one would ultimately wind up re-implementing the other two packages and this wouldn’t be worth the effort, of course.










share|improve this question


























    up vote
    0
    down vote

    favorite












    In this other question from 2012, a concise and functional solution has been suggested that merges tabulary and longtable into a new ltabulary.



    Is there any way to adjust this patch to work for tabularx instead of tabulary as well?



    Yes, for tabularx, there are ltablex and ltxtable. But if you don’t need extended features such as repeating headers, the minimal solution without an additional package, with reduced complexity, and with familiar syntax and usage is great to have, isn’t it?



    Now simply replacing tabulary with tabularx in the patch does not work, as it has other constructs such as TY@final, endTY@final and TY@tabular that I don’t know the equivalent replacements for.



    Perhaps one could find these in the source code for ltablex (about 99 lines apparently) or ltxtable (about 129 lines apparently).



    If there are similarly concise replacements and the ported patch can be completed, it would be interesting to know how this can be done. On the other hand, it the patch requires more code for tabularx than for tabulary, one would ultimately wind up re-implementing the other two packages and this wouldn’t be worth the effort, of course.










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      In this other question from 2012, a concise and functional solution has been suggested that merges tabulary and longtable into a new ltabulary.



      Is there any way to adjust this patch to work for tabularx instead of tabulary as well?



      Yes, for tabularx, there are ltablex and ltxtable. But if you don’t need extended features such as repeating headers, the minimal solution without an additional package, with reduced complexity, and with familiar syntax and usage is great to have, isn’t it?



      Now simply replacing tabulary with tabularx in the patch does not work, as it has other constructs such as TY@final, endTY@final and TY@tabular that I don’t know the equivalent replacements for.



      Perhaps one could find these in the source code for ltablex (about 99 lines apparently) or ltxtable (about 129 lines apparently).



      If there are similarly concise replacements and the ported patch can be completed, it would be interesting to know how this can be done. On the other hand, it the patch requires more code for tabularx than for tabulary, one would ultimately wind up re-implementing the other two packages and this wouldn’t be worth the effort, of course.










      share|improve this question













      In this other question from 2012, a concise and functional solution has been suggested that merges tabulary and longtable into a new ltabulary.



      Is there any way to adjust this patch to work for tabularx instead of tabulary as well?



      Yes, for tabularx, there are ltablex and ltxtable. But if you don’t need extended features such as repeating headers, the minimal solution without an additional package, with reduced complexity, and with familiar syntax and usage is great to have, isn’t it?



      Now simply replacing tabulary with tabularx in the patch does not work, as it has other constructs such as TY@final, endTY@final and TY@tabular that I don’t know the equivalent replacements for.



      Perhaps one could find these in the source code for ltablex (about 99 lines apparently) or ltxtable (about 129 lines apparently).



      If there are similarly concise replacements and the ported patch can be completed, it would be interesting to know how this can be done. On the other hand, it the patch requires more code for tabularx than for tabulary, one would ultimately wind up re-implementing the other two packages and this wouldn’t be worth the effort, of course.







      tables longtable tabularx tabulary






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 2 at 22:40









      caw

      121112




      121112



























          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%2f462868%2fmerge-tabularx-and-longtable-with-small-patch-instead-of-additional-package%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




















































          Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f462868%2fmerge-tabularx-and-longtable-with-small-patch-instead-of-additional-package%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

          Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

          ComboBox Display Member on multiple fields

          Is it possible to collect Nectar points via Trainline?