Setting a new entrytype












6














Doing as it has been suggested on this site, and also having looked in the manual for biblatex.pdf, I cannot figure out the difference between DeclareDatamodeFields and DeclareDatamodeEntryfields. I only get the address field as the result (Paris in this case). pdflatex, biber.



MWE



documentclass{article}
usepackage[datamodel=manuscript,bibstyle=verbose,citestyle=verbose]{biblatex}
begin{filecontents}{manuscript.dbx}
DeclareDatamodelEntrytypes{manuscript}
DeclareDatamodelFields[type=field, datatype=literal]{datation,title,library}
DeclareDatamodelEntryfields[manuscript]{
title,
library,
datation}
end{filecontents}
begin{filecontents}{maniscript.bib}
@manuscript{P1470,
library={BNF},
address={Paris},
datation={textsc{viii}textsuperscript{e} s.}
end{filecontents}

bibliography{manuscript.bib}
begin{document}
nocite{*}

printbibliography
end{document}









share|improve this question









New contributor




Dmitry Starostin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    6














    Doing as it has been suggested on this site, and also having looked in the manual for biblatex.pdf, I cannot figure out the difference between DeclareDatamodeFields and DeclareDatamodeEntryfields. I only get the address field as the result (Paris in this case). pdflatex, biber.



    MWE



    documentclass{article}
    usepackage[datamodel=manuscript,bibstyle=verbose,citestyle=verbose]{biblatex}
    begin{filecontents}{manuscript.dbx}
    DeclareDatamodelEntrytypes{manuscript}
    DeclareDatamodelFields[type=field, datatype=literal]{datation,title,library}
    DeclareDatamodelEntryfields[manuscript]{
    title,
    library,
    datation}
    end{filecontents}
    begin{filecontents}{maniscript.bib}
    @manuscript{P1470,
    library={BNF},
    address={Paris},
    datation={textsc{viii}textsuperscript{e} s.}
    end{filecontents}

    bibliography{manuscript.bib}
    begin{document}
    nocite{*}

    printbibliography
    end{document}









    share|improve this question









    New contributor




    Dmitry Starostin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      6












      6








      6


      0





      Doing as it has been suggested on this site, and also having looked in the manual for biblatex.pdf, I cannot figure out the difference between DeclareDatamodeFields and DeclareDatamodeEntryfields. I only get the address field as the result (Paris in this case). pdflatex, biber.



      MWE



      documentclass{article}
      usepackage[datamodel=manuscript,bibstyle=verbose,citestyle=verbose]{biblatex}
      begin{filecontents}{manuscript.dbx}
      DeclareDatamodelEntrytypes{manuscript}
      DeclareDatamodelFields[type=field, datatype=literal]{datation,title,library}
      DeclareDatamodelEntryfields[manuscript]{
      title,
      library,
      datation}
      end{filecontents}
      begin{filecontents}{maniscript.bib}
      @manuscript{P1470,
      library={BNF},
      address={Paris},
      datation={textsc{viii}textsuperscript{e} s.}
      end{filecontents}

      bibliography{manuscript.bib}
      begin{document}
      nocite{*}

      printbibliography
      end{document}









      share|improve this question









      New contributor




      Dmitry Starostin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      Doing as it has been suggested on this site, and also having looked in the manual for biblatex.pdf, I cannot figure out the difference between DeclareDatamodeFields and DeclareDatamodeEntryfields. I only get the address field as the result (Paris in this case). pdflatex, biber.



      MWE



      documentclass{article}
      usepackage[datamodel=manuscript,bibstyle=verbose,citestyle=verbose]{biblatex}
      begin{filecontents}{manuscript.dbx}
      DeclareDatamodelEntrytypes{manuscript}
      DeclareDatamodelFields[type=field, datatype=literal]{datation,title,library}
      DeclareDatamodelEntryfields[manuscript]{
      title,
      library,
      datation}
      end{filecontents}
      begin{filecontents}{maniscript.bib}
      @manuscript{P1470,
      library={BNF},
      address={Paris},
      datation={textsc{viii}textsuperscript{e} s.}
      end{filecontents}

      bibliography{manuscript.bib}
      begin{document}
      nocite{*}

      printbibliography
      end{document}






      biblatex bibentry






      share|improve this question









      New contributor




      Dmitry Starostin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      Dmitry Starostin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited Dec 16 at 19:39









      samcarter

      85k794271




      85k794271






      New contributor




      Dmitry Starostin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked Dec 16 at 19:30









      Dmitry Starostin

      333




      333




      New contributor




      Dmitry Starostin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Dmitry Starostin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Dmitry Starostin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          1 Answer
          1






          active

          oldest

          votes


















          6














          You are actually pretty close. If you look at moewe's canonical answer on the topic you can get a better grasp on the possibilities and requirements of creating a new entrytype.



          Still, to get your new fields typeset in the bibliography, you are critically missing a driver for you manuscript entrytype. I'm not sure the format you are looking for, but this serves as an example:



          DeclareBibliographyDriver{manuscript}{%
          usebibmacro{begentry}%
          printfield{library}%
          setunit{addcommaspace}%
          printlist{location}%
          newunitnewblock
          printfield{title}%
          setunit{addcommaspace}%
          printfield{datation}%
          usebibmacro{finentry}%
          }


          I've also removed title and library from your .dbx file, as they are already defined by default. You should still add them to your DeclareDatamodelEntryfields[manuscript]{... as you do. Also, note that setting both citestyle and bibstyle to verbose is equivalent to the more direct style=verbose.



          In full:



          documentclass{article}

          usepackage[datamodel=manuscript,style=verbose]{biblatex}

          usepackage{filecontents}

          begin{filecontents}{manuscript.dbx}
          DeclareDatamodelEntrytypes{manuscript}
          DeclareDatamodelFields[type=field, datatype=literal]{datation}
          DeclareDatamodelEntryfields[manuscript]{
          title,
          library,
          location,
          datation}
          end{filecontents}

          begin{filecontents}{manuscript.bib}
          @manuscript{P1470,
          library = {BNF},
          title = {A title},
          location = {Paris},
          datation = {textsc{viii}textsuperscript{e} s.},
          }
          end{filecontents}

          DeclareBibliographyDriver{manuscript}{%
          usebibmacro{begentry}%
          printfield{library}%
          setunit{addcommaspace}%
          printlist{location}%
          newunitnewblock
          printfield{title}%
          setunit{addcommaspace}%
          printfield{datation}%
          usebibmacro{finentry}%
          }

          DeclareFieldFormat[manuscript]{title}{mkbibquote{#1isdot}}

          addbibresource{manuscript.bib}

          begin{document}
          nocite{*}
          printbibliography
          end{document}


          enter image description here



          You can, and should, examine closer moewe's linked answer, particularly the formatting directives. Also, you can redefine your bibdriver to the order of fields and punctuation of your liking.






          share|improve this answer























          • Thank you very much! You explained by a very clear and hands-on code what I have long tried to master.
            – Dmitry Starostin
            Dec 16 at 21:23










          • Thank you for laying all out in such a complete reply. The need for such consultation emerges for people like me because I have only been trained in programming languages like Fortran77, Algol, and a bit of Pascal, and every step (1. Data model 2.driver 3. field format requires a conceptual "retooling". :) Making a driver can still be grasped, but "DeclareFieldFormat", frankly, was beyond my conceptual reach even though I read the manual. :)
            – Dmitry Starostin
            Dec 17 at 10:36










          • @DmitryStarostin Indeed, biblatex's jargon needs some getting used to, but once you grasp it you'll see it has a logic. I hope it has been enough to get you started. moewe's answer, specially, is very thorough. But old time languages should be no impediment. I started myself with Basic on a TK85 (a ZX81 clone) with K7 tape memory and all! :)
            – gusbrs
            Dec 17 at 11:12






          • 1




            Thank you! It does have logic indeed, one just has to get accustomed to the relatively "slow" flow of definitions, which are nevertheless all conceptually justified. I have been using Latex for about ten years now, and it has been teaching me a very high-level philosophy of programming. It is not only Turing-complete, it does have a very precise conceptual definition of every step that has taught me since to at least understand such languages as Python and Java.
            – Dmitry Starostin
            Dec 18 at 15:27











          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',
          autoActivateHeartbeat: false,
          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
          });


          }
          });






          Dmitry Starostin is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f466120%2fsetting-a-new-entrytype%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          6














          You are actually pretty close. If you look at moewe's canonical answer on the topic you can get a better grasp on the possibilities and requirements of creating a new entrytype.



          Still, to get your new fields typeset in the bibliography, you are critically missing a driver for you manuscript entrytype. I'm not sure the format you are looking for, but this serves as an example:



          DeclareBibliographyDriver{manuscript}{%
          usebibmacro{begentry}%
          printfield{library}%
          setunit{addcommaspace}%
          printlist{location}%
          newunitnewblock
          printfield{title}%
          setunit{addcommaspace}%
          printfield{datation}%
          usebibmacro{finentry}%
          }


          I've also removed title and library from your .dbx file, as they are already defined by default. You should still add them to your DeclareDatamodelEntryfields[manuscript]{... as you do. Also, note that setting both citestyle and bibstyle to verbose is equivalent to the more direct style=verbose.



          In full:



          documentclass{article}

          usepackage[datamodel=manuscript,style=verbose]{biblatex}

          usepackage{filecontents}

          begin{filecontents}{manuscript.dbx}
          DeclareDatamodelEntrytypes{manuscript}
          DeclareDatamodelFields[type=field, datatype=literal]{datation}
          DeclareDatamodelEntryfields[manuscript]{
          title,
          library,
          location,
          datation}
          end{filecontents}

          begin{filecontents}{manuscript.bib}
          @manuscript{P1470,
          library = {BNF},
          title = {A title},
          location = {Paris},
          datation = {textsc{viii}textsuperscript{e} s.},
          }
          end{filecontents}

          DeclareBibliographyDriver{manuscript}{%
          usebibmacro{begentry}%
          printfield{library}%
          setunit{addcommaspace}%
          printlist{location}%
          newunitnewblock
          printfield{title}%
          setunit{addcommaspace}%
          printfield{datation}%
          usebibmacro{finentry}%
          }

          DeclareFieldFormat[manuscript]{title}{mkbibquote{#1isdot}}

          addbibresource{manuscript.bib}

          begin{document}
          nocite{*}
          printbibliography
          end{document}


          enter image description here



          You can, and should, examine closer moewe's linked answer, particularly the formatting directives. Also, you can redefine your bibdriver to the order of fields and punctuation of your liking.






          share|improve this answer























          • Thank you very much! You explained by a very clear and hands-on code what I have long tried to master.
            – Dmitry Starostin
            Dec 16 at 21:23










          • Thank you for laying all out in such a complete reply. The need for such consultation emerges for people like me because I have only been trained in programming languages like Fortran77, Algol, and a bit of Pascal, and every step (1. Data model 2.driver 3. field format requires a conceptual "retooling". :) Making a driver can still be grasped, but "DeclareFieldFormat", frankly, was beyond my conceptual reach even though I read the manual. :)
            – Dmitry Starostin
            Dec 17 at 10:36










          • @DmitryStarostin Indeed, biblatex's jargon needs some getting used to, but once you grasp it you'll see it has a logic. I hope it has been enough to get you started. moewe's answer, specially, is very thorough. But old time languages should be no impediment. I started myself with Basic on a TK85 (a ZX81 clone) with K7 tape memory and all! :)
            – gusbrs
            Dec 17 at 11:12






          • 1




            Thank you! It does have logic indeed, one just has to get accustomed to the relatively "slow" flow of definitions, which are nevertheless all conceptually justified. I have been using Latex for about ten years now, and it has been teaching me a very high-level philosophy of programming. It is not only Turing-complete, it does have a very precise conceptual definition of every step that has taught me since to at least understand such languages as Python and Java.
            – Dmitry Starostin
            Dec 18 at 15:27
















          6














          You are actually pretty close. If you look at moewe's canonical answer on the topic you can get a better grasp on the possibilities and requirements of creating a new entrytype.



          Still, to get your new fields typeset in the bibliography, you are critically missing a driver for you manuscript entrytype. I'm not sure the format you are looking for, but this serves as an example:



          DeclareBibliographyDriver{manuscript}{%
          usebibmacro{begentry}%
          printfield{library}%
          setunit{addcommaspace}%
          printlist{location}%
          newunitnewblock
          printfield{title}%
          setunit{addcommaspace}%
          printfield{datation}%
          usebibmacro{finentry}%
          }


          I've also removed title and library from your .dbx file, as they are already defined by default. You should still add them to your DeclareDatamodelEntryfields[manuscript]{... as you do. Also, note that setting both citestyle and bibstyle to verbose is equivalent to the more direct style=verbose.



          In full:



          documentclass{article}

          usepackage[datamodel=manuscript,style=verbose]{biblatex}

          usepackage{filecontents}

          begin{filecontents}{manuscript.dbx}
          DeclareDatamodelEntrytypes{manuscript}
          DeclareDatamodelFields[type=field, datatype=literal]{datation}
          DeclareDatamodelEntryfields[manuscript]{
          title,
          library,
          location,
          datation}
          end{filecontents}

          begin{filecontents}{manuscript.bib}
          @manuscript{P1470,
          library = {BNF},
          title = {A title},
          location = {Paris},
          datation = {textsc{viii}textsuperscript{e} s.},
          }
          end{filecontents}

          DeclareBibliographyDriver{manuscript}{%
          usebibmacro{begentry}%
          printfield{library}%
          setunit{addcommaspace}%
          printlist{location}%
          newunitnewblock
          printfield{title}%
          setunit{addcommaspace}%
          printfield{datation}%
          usebibmacro{finentry}%
          }

          DeclareFieldFormat[manuscript]{title}{mkbibquote{#1isdot}}

          addbibresource{manuscript.bib}

          begin{document}
          nocite{*}
          printbibliography
          end{document}


          enter image description here



          You can, and should, examine closer moewe's linked answer, particularly the formatting directives. Also, you can redefine your bibdriver to the order of fields and punctuation of your liking.






          share|improve this answer























          • Thank you very much! You explained by a very clear and hands-on code what I have long tried to master.
            – Dmitry Starostin
            Dec 16 at 21:23










          • Thank you for laying all out in such a complete reply. The need for such consultation emerges for people like me because I have only been trained in programming languages like Fortran77, Algol, and a bit of Pascal, and every step (1. Data model 2.driver 3. field format requires a conceptual "retooling". :) Making a driver can still be grasped, but "DeclareFieldFormat", frankly, was beyond my conceptual reach even though I read the manual. :)
            – Dmitry Starostin
            Dec 17 at 10:36










          • @DmitryStarostin Indeed, biblatex's jargon needs some getting used to, but once you grasp it you'll see it has a logic. I hope it has been enough to get you started. moewe's answer, specially, is very thorough. But old time languages should be no impediment. I started myself with Basic on a TK85 (a ZX81 clone) with K7 tape memory and all! :)
            – gusbrs
            Dec 17 at 11:12






          • 1




            Thank you! It does have logic indeed, one just has to get accustomed to the relatively "slow" flow of definitions, which are nevertheless all conceptually justified. I have been using Latex for about ten years now, and it has been teaching me a very high-level philosophy of programming. It is not only Turing-complete, it does have a very precise conceptual definition of every step that has taught me since to at least understand such languages as Python and Java.
            – Dmitry Starostin
            Dec 18 at 15:27














          6












          6








          6






          You are actually pretty close. If you look at moewe's canonical answer on the topic you can get a better grasp on the possibilities and requirements of creating a new entrytype.



          Still, to get your new fields typeset in the bibliography, you are critically missing a driver for you manuscript entrytype. I'm not sure the format you are looking for, but this serves as an example:



          DeclareBibliographyDriver{manuscript}{%
          usebibmacro{begentry}%
          printfield{library}%
          setunit{addcommaspace}%
          printlist{location}%
          newunitnewblock
          printfield{title}%
          setunit{addcommaspace}%
          printfield{datation}%
          usebibmacro{finentry}%
          }


          I've also removed title and library from your .dbx file, as they are already defined by default. You should still add them to your DeclareDatamodelEntryfields[manuscript]{... as you do. Also, note that setting both citestyle and bibstyle to verbose is equivalent to the more direct style=verbose.



          In full:



          documentclass{article}

          usepackage[datamodel=manuscript,style=verbose]{biblatex}

          usepackage{filecontents}

          begin{filecontents}{manuscript.dbx}
          DeclareDatamodelEntrytypes{manuscript}
          DeclareDatamodelFields[type=field, datatype=literal]{datation}
          DeclareDatamodelEntryfields[manuscript]{
          title,
          library,
          location,
          datation}
          end{filecontents}

          begin{filecontents}{manuscript.bib}
          @manuscript{P1470,
          library = {BNF},
          title = {A title},
          location = {Paris},
          datation = {textsc{viii}textsuperscript{e} s.},
          }
          end{filecontents}

          DeclareBibliographyDriver{manuscript}{%
          usebibmacro{begentry}%
          printfield{library}%
          setunit{addcommaspace}%
          printlist{location}%
          newunitnewblock
          printfield{title}%
          setunit{addcommaspace}%
          printfield{datation}%
          usebibmacro{finentry}%
          }

          DeclareFieldFormat[manuscript]{title}{mkbibquote{#1isdot}}

          addbibresource{manuscript.bib}

          begin{document}
          nocite{*}
          printbibliography
          end{document}


          enter image description here



          You can, and should, examine closer moewe's linked answer, particularly the formatting directives. Also, you can redefine your bibdriver to the order of fields and punctuation of your liking.






          share|improve this answer














          You are actually pretty close. If you look at moewe's canonical answer on the topic you can get a better grasp on the possibilities and requirements of creating a new entrytype.



          Still, to get your new fields typeset in the bibliography, you are critically missing a driver for you manuscript entrytype. I'm not sure the format you are looking for, but this serves as an example:



          DeclareBibliographyDriver{manuscript}{%
          usebibmacro{begentry}%
          printfield{library}%
          setunit{addcommaspace}%
          printlist{location}%
          newunitnewblock
          printfield{title}%
          setunit{addcommaspace}%
          printfield{datation}%
          usebibmacro{finentry}%
          }


          I've also removed title and library from your .dbx file, as they are already defined by default. You should still add them to your DeclareDatamodelEntryfields[manuscript]{... as you do. Also, note that setting both citestyle and bibstyle to verbose is equivalent to the more direct style=verbose.



          In full:



          documentclass{article}

          usepackage[datamodel=manuscript,style=verbose]{biblatex}

          usepackage{filecontents}

          begin{filecontents}{manuscript.dbx}
          DeclareDatamodelEntrytypes{manuscript}
          DeclareDatamodelFields[type=field, datatype=literal]{datation}
          DeclareDatamodelEntryfields[manuscript]{
          title,
          library,
          location,
          datation}
          end{filecontents}

          begin{filecontents}{manuscript.bib}
          @manuscript{P1470,
          library = {BNF},
          title = {A title},
          location = {Paris},
          datation = {textsc{viii}textsuperscript{e} s.},
          }
          end{filecontents}

          DeclareBibliographyDriver{manuscript}{%
          usebibmacro{begentry}%
          printfield{library}%
          setunit{addcommaspace}%
          printlist{location}%
          newunitnewblock
          printfield{title}%
          setunit{addcommaspace}%
          printfield{datation}%
          usebibmacro{finentry}%
          }

          DeclareFieldFormat[manuscript]{title}{mkbibquote{#1isdot}}

          addbibresource{manuscript.bib}

          begin{document}
          nocite{*}
          printbibliography
          end{document}


          enter image description here



          You can, and should, examine closer moewe's linked answer, particularly the formatting directives. Also, you can redefine your bibdriver to the order of fields and punctuation of your liking.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Dec 16 at 21:41









          moewe

          85.7k9109331




          85.7k9109331










          answered Dec 16 at 20:21









          gusbrs

          6,9442839




          6,9442839












          • Thank you very much! You explained by a very clear and hands-on code what I have long tried to master.
            – Dmitry Starostin
            Dec 16 at 21:23










          • Thank you for laying all out in such a complete reply. The need for such consultation emerges for people like me because I have only been trained in programming languages like Fortran77, Algol, and a bit of Pascal, and every step (1. Data model 2.driver 3. field format requires a conceptual "retooling". :) Making a driver can still be grasped, but "DeclareFieldFormat", frankly, was beyond my conceptual reach even though I read the manual. :)
            – Dmitry Starostin
            Dec 17 at 10:36










          • @DmitryStarostin Indeed, biblatex's jargon needs some getting used to, but once you grasp it you'll see it has a logic. I hope it has been enough to get you started. moewe's answer, specially, is very thorough. But old time languages should be no impediment. I started myself with Basic on a TK85 (a ZX81 clone) with K7 tape memory and all! :)
            – gusbrs
            Dec 17 at 11:12






          • 1




            Thank you! It does have logic indeed, one just has to get accustomed to the relatively "slow" flow of definitions, which are nevertheless all conceptually justified. I have been using Latex for about ten years now, and it has been teaching me a very high-level philosophy of programming. It is not only Turing-complete, it does have a very precise conceptual definition of every step that has taught me since to at least understand such languages as Python and Java.
            – Dmitry Starostin
            Dec 18 at 15:27


















          • Thank you very much! You explained by a very clear and hands-on code what I have long tried to master.
            – Dmitry Starostin
            Dec 16 at 21:23










          • Thank you for laying all out in such a complete reply. The need for such consultation emerges for people like me because I have only been trained in programming languages like Fortran77, Algol, and a bit of Pascal, and every step (1. Data model 2.driver 3. field format requires a conceptual "retooling". :) Making a driver can still be grasped, but "DeclareFieldFormat", frankly, was beyond my conceptual reach even though I read the manual. :)
            – Dmitry Starostin
            Dec 17 at 10:36










          • @DmitryStarostin Indeed, biblatex's jargon needs some getting used to, but once you grasp it you'll see it has a logic. I hope it has been enough to get you started. moewe's answer, specially, is very thorough. But old time languages should be no impediment. I started myself with Basic on a TK85 (a ZX81 clone) with K7 tape memory and all! :)
            – gusbrs
            Dec 17 at 11:12






          • 1




            Thank you! It does have logic indeed, one just has to get accustomed to the relatively "slow" flow of definitions, which are nevertheless all conceptually justified. I have been using Latex for about ten years now, and it has been teaching me a very high-level philosophy of programming. It is not only Turing-complete, it does have a very precise conceptual definition of every step that has taught me since to at least understand such languages as Python and Java.
            – Dmitry Starostin
            Dec 18 at 15:27
















          Thank you very much! You explained by a very clear and hands-on code what I have long tried to master.
          – Dmitry Starostin
          Dec 16 at 21:23




          Thank you very much! You explained by a very clear and hands-on code what I have long tried to master.
          – Dmitry Starostin
          Dec 16 at 21:23












          Thank you for laying all out in such a complete reply. The need for such consultation emerges for people like me because I have only been trained in programming languages like Fortran77, Algol, and a bit of Pascal, and every step (1. Data model 2.driver 3. field format requires a conceptual "retooling". :) Making a driver can still be grasped, but "DeclareFieldFormat", frankly, was beyond my conceptual reach even though I read the manual. :)
          – Dmitry Starostin
          Dec 17 at 10:36




          Thank you for laying all out in such a complete reply. The need for such consultation emerges for people like me because I have only been trained in programming languages like Fortran77, Algol, and a bit of Pascal, and every step (1. Data model 2.driver 3. field format requires a conceptual "retooling". :) Making a driver can still be grasped, but "DeclareFieldFormat", frankly, was beyond my conceptual reach even though I read the manual. :)
          – Dmitry Starostin
          Dec 17 at 10:36












          @DmitryStarostin Indeed, biblatex's jargon needs some getting used to, but once you grasp it you'll see it has a logic. I hope it has been enough to get you started. moewe's answer, specially, is very thorough. But old time languages should be no impediment. I started myself with Basic on a TK85 (a ZX81 clone) with K7 tape memory and all! :)
          – gusbrs
          Dec 17 at 11:12




          @DmitryStarostin Indeed, biblatex's jargon needs some getting used to, but once you grasp it you'll see it has a logic. I hope it has been enough to get you started. moewe's answer, specially, is very thorough. But old time languages should be no impediment. I started myself with Basic on a TK85 (a ZX81 clone) with K7 tape memory and all! :)
          – gusbrs
          Dec 17 at 11:12




          1




          1




          Thank you! It does have logic indeed, one just has to get accustomed to the relatively "slow" flow of definitions, which are nevertheless all conceptually justified. I have been using Latex for about ten years now, and it has been teaching me a very high-level philosophy of programming. It is not only Turing-complete, it does have a very precise conceptual definition of every step that has taught me since to at least understand such languages as Python and Java.
          – Dmitry Starostin
          Dec 18 at 15:27




          Thank you! It does have logic indeed, one just has to get accustomed to the relatively "slow" flow of definitions, which are nevertheless all conceptually justified. I have been using Latex for about ten years now, and it has been teaching me a very high-level philosophy of programming. It is not only Turing-complete, it does have a very precise conceptual definition of every step that has taught me since to at least understand such languages as Python and Java.
          – Dmitry Starostin
          Dec 18 at 15:27










          Dmitry Starostin is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Dmitry Starostin is a new contributor. Be nice, and check out our Code of Conduct.













          Dmitry Starostin is a new contributor. Be nice, and check out our Code of Conduct.












          Dmitry Starostin is a new contributor. Be nice, and check out our Code of Conduct.
















          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%2f466120%2fsetting-a-new-entrytype%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

          數位音樂下載

          When can things happen in Etherscan, such as the picture below?

          格利澤436b