make tex glossaries files accessible for all documents across systemWhere do I place my own .sty or .cls files, to make them available to all my .tex files?Create separate list of acronyms and glossaryMiKTeX / TeXnicCenter / Adobe Reader: No pdf producedMikTeX Deployment for multiple usersMiKTeX Installation Fails with “Executed process did not succeed”LaTeX can't find main.tex file in certain directoriesAutomatically extracting files from archive before compilationMiktex not working for beamer presentationBibtex can't find biblatex.bstMaking subdirectories for each .tex document (with AUX files) but still access .bib file at higher directoryMiKTeX installation error: access violation issueIdentify basic packages required to create PDF from tex file without installing MikTex software

Python if-else code style for reduced code for rounding floats

Why does energy conservation give me the wrong answer in this inelastic collision problem?

Why Choose Less Effective Armour Types?

PTIJ: Who should I vote for? (21st Knesset Edition)

What is the Japanese sound word for the clinking of money?

Meme-controlled people

Is it true that good novels will automatically sell themselves on Amazon (and so on) and there is no need for one to waste time promoting?

Is a party consisting of only a bard, a cleric, and a warlock functional long-term?

Why do tuner card drivers fail to build after kernel update to 4.4.0-143-generic?

Why one should not leave fingerprints on bulbs and plugs?

Recruiter wants very extensive technical details about all of my previous work

Bacteria contamination inside a thermos bottle

Aluminum electrolytic or ceramic capacitors for linear regulator input and output?

Did Ender ever learn that he killed Stilson and/or Bonzo?

I got the following comment from a reputed math journal. What does it mean?

I am confused as to how the inverse of a certain function is found.

Why do newer 737s use two different styles of split winglets?

Examples of transfinite towers

How do I change two letters closest to a string and one letter immediately after a string using Notepad++?

How to write cleanly even if my character uses expletive language?

Instead of a Universal Basic Income program, why not implement a "Universal Basic Needs" program?

Math equation in non italic font

Problem with FindRoot

Book about superhumans hiding among normal humans



make tex glossaries files accessible for all documents across system


Where do I place my own .sty or .cls files, to make them available to all my .tex files?Create separate list of acronyms and glossaryMiKTeX / TeXnicCenter / Adobe Reader: No pdf producedMikTeX Deployment for multiple usersMiKTeX Installation Fails with “Executed process did not succeed”LaTeX can't find main.tex file in certain directoriesAutomatically extracting files from archive before compilationMiktex not working for beamer presentationBibtex can't find biblatex.bstMaking subdirectories for each .tex document (with AUX files) but still access .bib file at higher directoryMiKTeX installation error: access violation issueIdentify basic packages required to create PDF from tex file without installing MikTex software













0















I created some rather big glossaries files with symbols, acronyms, ... for a programming project with multiple tex documents as their documentation. Each glossaries file is a single tex file for reuse throughout the multiple documents of the project. The document is part of a SVN repository. I created a single common directory to store files that are used in all tex documents throughout the repository. I managed to access this common directory by definition of



newcommandcommonpath../Common


and added the paths to the single documents relatively using this path statement.



Now I want to write a new document as part of a another SVN repository and re-use the same glossaries files. I could of course copy the files to the new project. However, I want to keep one common "language" throughout all of my documents. Thus, I would rather work and change one single file at a single location rather than to keep multiple files synchronized. For my local installation I now the relative positioning of the two repositories and their tex documents with respect to each other. However, if a 3rd person checks out both SVN repositories, I cannot assure that they use the same relative path of the 2 repository checkouts.



How can I access the glossaries files from multiple projects? I am on Windows using MikTeX 2.9. Is there a possibility to make single tex files available throughout the system, e.g. via the directories path of the MikTeX Console? Or is it preferable to pack the files into a new package to deploy myself?



Can someone please give me some hints? What is the best way?










share|improve this question




























    0















    I created some rather big glossaries files with symbols, acronyms, ... for a programming project with multiple tex documents as their documentation. Each glossaries file is a single tex file for reuse throughout the multiple documents of the project. The document is part of a SVN repository. I created a single common directory to store files that are used in all tex documents throughout the repository. I managed to access this common directory by definition of



    newcommandcommonpath../Common


    and added the paths to the single documents relatively using this path statement.



    Now I want to write a new document as part of a another SVN repository and re-use the same glossaries files. I could of course copy the files to the new project. However, I want to keep one common "language" throughout all of my documents. Thus, I would rather work and change one single file at a single location rather than to keep multiple files synchronized. For my local installation I now the relative positioning of the two repositories and their tex documents with respect to each other. However, if a 3rd person checks out both SVN repositories, I cannot assure that they use the same relative path of the 2 repository checkouts.



    How can I access the glossaries files from multiple projects? I am on Windows using MikTeX 2.9. Is there a possibility to make single tex files available throughout the system, e.g. via the directories path of the MikTeX Console? Or is it preferable to pack the files into a new package to deploy myself?



    Can someone please give me some hints? What is the best way?










    share|improve this question


























      0












      0








      0








      I created some rather big glossaries files with symbols, acronyms, ... for a programming project with multiple tex documents as their documentation. Each glossaries file is a single tex file for reuse throughout the multiple documents of the project. The document is part of a SVN repository. I created a single common directory to store files that are used in all tex documents throughout the repository. I managed to access this common directory by definition of



      newcommandcommonpath../Common


      and added the paths to the single documents relatively using this path statement.



      Now I want to write a new document as part of a another SVN repository and re-use the same glossaries files. I could of course copy the files to the new project. However, I want to keep one common "language" throughout all of my documents. Thus, I would rather work and change one single file at a single location rather than to keep multiple files synchronized. For my local installation I now the relative positioning of the two repositories and their tex documents with respect to each other. However, if a 3rd person checks out both SVN repositories, I cannot assure that they use the same relative path of the 2 repository checkouts.



      How can I access the glossaries files from multiple projects? I am on Windows using MikTeX 2.9. Is there a possibility to make single tex files available throughout the system, e.g. via the directories path of the MikTeX Console? Or is it preferable to pack the files into a new package to deploy myself?



      Can someone please give me some hints? What is the best way?










      share|improve this question
















      I created some rather big glossaries files with symbols, acronyms, ... for a programming project with multiple tex documents as their documentation. Each glossaries file is a single tex file for reuse throughout the multiple documents of the project. The document is part of a SVN repository. I created a single common directory to store files that are used in all tex documents throughout the repository. I managed to access this common directory by definition of



      newcommandcommonpath../Common


      and added the paths to the single documents relatively using this path statement.



      Now I want to write a new document as part of a another SVN repository and re-use the same glossaries files. I could of course copy the files to the new project. However, I want to keep one common "language" throughout all of my documents. Thus, I would rather work and change one single file at a single location rather than to keep multiple files synchronized. For my local installation I now the relative positioning of the two repositories and their tex documents with respect to each other. However, if a 3rd person checks out both SVN repositories, I cannot assure that they use the same relative path of the 2 repository checkouts.



      How can I access the glossaries files from multiple projects? I am on Windows using MikTeX 2.9. Is there a possibility to make single tex files available throughout the system, e.g. via the directories path of the MikTeX Console? Or is it preferable to pack the files into a new package to deploy myself?



      Can someone please give me some hints? What is the best way?







      miktex glossaries filesystem-access directory






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 5 mins ago









      KJO

      3,0681120




      3,0681120










      asked 4 hours ago









      krtekkrtek

      890820




      890820




















          1 Answer
          1






          active

          oldest

          votes


















          1














          There are those much better qualified than me to answer, so feel free to accept a later answer however you asked for hints and there is perhaps too much for mere comments.



          Your tags need changing to attract focused answers so I will alter some. It would also help if you describe your system architecture such as are all users one of Windows / Linux / Mac and are the files checked out from SVN via mapped drives etc. (beware mapped drives that have underlying spaces accents etc.)



          Do all users use an IDE (which) or do some need command line compilation ?



          How do you address auxdirs such as TEXINPUTS= since MiKTeX has a slightly different pathing structure compared to say TeX Live ?



          Do you use xindy or only makeindex ?

          Do you use command aggregation such as arara or latexmk ?

          How do you handle build directories are all aux files in the same directory as the main.tex



          Your specific query for glossaries is perhaps suited to section 7.3 in https://en.wikibooks.org/wiki/LaTeX/Glossary#Glossary_definitions



          and for a related acronyms Question/Answer here
          Create separate list of acronyms and glossary






          share|improve this answer

























          • +1 for helping him/her after so much time... But adding also a way as an example like using a non-relative but an absolute path would make your question better and reviewers would not recommend deletion in any case ;) (But I haven't really understood the question enough)

            – koleygr
            28 mins ago












          • @koleygr I am trying not to ask in 20 different comments what type of relative / absolute path we are dealing with I have absolutely no experience with e.g. docker

            – KJO
            25 mins ago











          • I mean that possibly adding newcommandcommonpath/home/<username>/Common could solve the problem and you don't have to be specific here... Just shared the idea... But again.. I didn't understood the problem in the question yet. (I just think that some answer similar to any answer of this tex.stackexchange.com/q/1137/120578 could be a possible answer as far as I can understand the question)

            – koleygr
            17 mins ago






          • 1





            @koleygr I agree for sty files there are many answers but xindy has its own variables and AFAIK glossaries as built at compilation time by the tex file cannot be easily collated from a central location, but I have not tried out glossaries enough to do otherwise :-)

            – KJO
            9 mins ago






          • 1





            Thanks... didn't noticed that... Actually I don't have the needed experience with glossaries too.

            – koleygr
            4 mins ago










          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
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f479841%2fmake-tex-glossaries-files-accessible-for-all-documents-across-system%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









          1














          There are those much better qualified than me to answer, so feel free to accept a later answer however you asked for hints and there is perhaps too much for mere comments.



          Your tags need changing to attract focused answers so I will alter some. It would also help if you describe your system architecture such as are all users one of Windows / Linux / Mac and are the files checked out from SVN via mapped drives etc. (beware mapped drives that have underlying spaces accents etc.)



          Do all users use an IDE (which) or do some need command line compilation ?



          How do you address auxdirs such as TEXINPUTS= since MiKTeX has a slightly different pathing structure compared to say TeX Live ?



          Do you use xindy or only makeindex ?

          Do you use command aggregation such as arara or latexmk ?

          How do you handle build directories are all aux files in the same directory as the main.tex



          Your specific query for glossaries is perhaps suited to section 7.3 in https://en.wikibooks.org/wiki/LaTeX/Glossary#Glossary_definitions



          and for a related acronyms Question/Answer here
          Create separate list of acronyms and glossary






          share|improve this answer

























          • +1 for helping him/her after so much time... But adding also a way as an example like using a non-relative but an absolute path would make your question better and reviewers would not recommend deletion in any case ;) (But I haven't really understood the question enough)

            – koleygr
            28 mins ago












          • @koleygr I am trying not to ask in 20 different comments what type of relative / absolute path we are dealing with I have absolutely no experience with e.g. docker

            – KJO
            25 mins ago











          • I mean that possibly adding newcommandcommonpath/home/<username>/Common could solve the problem and you don't have to be specific here... Just shared the idea... But again.. I didn't understood the problem in the question yet. (I just think that some answer similar to any answer of this tex.stackexchange.com/q/1137/120578 could be a possible answer as far as I can understand the question)

            – koleygr
            17 mins ago






          • 1





            @koleygr I agree for sty files there are many answers but xindy has its own variables and AFAIK glossaries as built at compilation time by the tex file cannot be easily collated from a central location, but I have not tried out glossaries enough to do otherwise :-)

            – KJO
            9 mins ago






          • 1





            Thanks... didn't noticed that... Actually I don't have the needed experience with glossaries too.

            – koleygr
            4 mins ago















          1














          There are those much better qualified than me to answer, so feel free to accept a later answer however you asked for hints and there is perhaps too much for mere comments.



          Your tags need changing to attract focused answers so I will alter some. It would also help if you describe your system architecture such as are all users one of Windows / Linux / Mac and are the files checked out from SVN via mapped drives etc. (beware mapped drives that have underlying spaces accents etc.)



          Do all users use an IDE (which) or do some need command line compilation ?



          How do you address auxdirs such as TEXINPUTS= since MiKTeX has a slightly different pathing structure compared to say TeX Live ?



          Do you use xindy or only makeindex ?

          Do you use command aggregation such as arara or latexmk ?

          How do you handle build directories are all aux files in the same directory as the main.tex



          Your specific query for glossaries is perhaps suited to section 7.3 in https://en.wikibooks.org/wiki/LaTeX/Glossary#Glossary_definitions



          and for a related acronyms Question/Answer here
          Create separate list of acronyms and glossary






          share|improve this answer

























          • +1 for helping him/her after so much time... But adding also a way as an example like using a non-relative but an absolute path would make your question better and reviewers would not recommend deletion in any case ;) (But I haven't really understood the question enough)

            – koleygr
            28 mins ago












          • @koleygr I am trying not to ask in 20 different comments what type of relative / absolute path we are dealing with I have absolutely no experience with e.g. docker

            – KJO
            25 mins ago











          • I mean that possibly adding newcommandcommonpath/home/<username>/Common could solve the problem and you don't have to be specific here... Just shared the idea... But again.. I didn't understood the problem in the question yet. (I just think that some answer similar to any answer of this tex.stackexchange.com/q/1137/120578 could be a possible answer as far as I can understand the question)

            – koleygr
            17 mins ago






          • 1





            @koleygr I agree for sty files there are many answers but xindy has its own variables and AFAIK glossaries as built at compilation time by the tex file cannot be easily collated from a central location, but I have not tried out glossaries enough to do otherwise :-)

            – KJO
            9 mins ago






          • 1





            Thanks... didn't noticed that... Actually I don't have the needed experience with glossaries too.

            – koleygr
            4 mins ago













          1












          1








          1







          There are those much better qualified than me to answer, so feel free to accept a later answer however you asked for hints and there is perhaps too much for mere comments.



          Your tags need changing to attract focused answers so I will alter some. It would also help if you describe your system architecture such as are all users one of Windows / Linux / Mac and are the files checked out from SVN via mapped drives etc. (beware mapped drives that have underlying spaces accents etc.)



          Do all users use an IDE (which) or do some need command line compilation ?



          How do you address auxdirs such as TEXINPUTS= since MiKTeX has a slightly different pathing structure compared to say TeX Live ?



          Do you use xindy or only makeindex ?

          Do you use command aggregation such as arara or latexmk ?

          How do you handle build directories are all aux files in the same directory as the main.tex



          Your specific query for glossaries is perhaps suited to section 7.3 in https://en.wikibooks.org/wiki/LaTeX/Glossary#Glossary_definitions



          and for a related acronyms Question/Answer here
          Create separate list of acronyms and glossary






          share|improve this answer















          There are those much better qualified than me to answer, so feel free to accept a later answer however you asked for hints and there is perhaps too much for mere comments.



          Your tags need changing to attract focused answers so I will alter some. It would also help if you describe your system architecture such as are all users one of Windows / Linux / Mac and are the files checked out from SVN via mapped drives etc. (beware mapped drives that have underlying spaces accents etc.)



          Do all users use an IDE (which) or do some need command line compilation ?



          How do you address auxdirs such as TEXINPUTS= since MiKTeX has a slightly different pathing structure compared to say TeX Live ?



          Do you use xindy or only makeindex ?

          Do you use command aggregation such as arara or latexmk ?

          How do you handle build directories are all aux files in the same directory as the main.tex



          Your specific query for glossaries is perhaps suited to section 7.3 in https://en.wikibooks.org/wiki/LaTeX/Glossary#Glossary_definitions



          and for a related acronyms Question/Answer here
          Create separate list of acronyms and glossary







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 28 mins ago

























          answered 37 mins ago









          KJOKJO

          3,0681120




          3,0681120












          • +1 for helping him/her after so much time... But adding also a way as an example like using a non-relative but an absolute path would make your question better and reviewers would not recommend deletion in any case ;) (But I haven't really understood the question enough)

            – koleygr
            28 mins ago












          • @koleygr I am trying not to ask in 20 different comments what type of relative / absolute path we are dealing with I have absolutely no experience with e.g. docker

            – KJO
            25 mins ago











          • I mean that possibly adding newcommandcommonpath/home/<username>/Common could solve the problem and you don't have to be specific here... Just shared the idea... But again.. I didn't understood the problem in the question yet. (I just think that some answer similar to any answer of this tex.stackexchange.com/q/1137/120578 could be a possible answer as far as I can understand the question)

            – koleygr
            17 mins ago






          • 1





            @koleygr I agree for sty files there are many answers but xindy has its own variables and AFAIK glossaries as built at compilation time by the tex file cannot be easily collated from a central location, but I have not tried out glossaries enough to do otherwise :-)

            – KJO
            9 mins ago






          • 1





            Thanks... didn't noticed that... Actually I don't have the needed experience with glossaries too.

            – koleygr
            4 mins ago

















          • +1 for helping him/her after so much time... But adding also a way as an example like using a non-relative but an absolute path would make your question better and reviewers would not recommend deletion in any case ;) (But I haven't really understood the question enough)

            – koleygr
            28 mins ago












          • @koleygr I am trying not to ask in 20 different comments what type of relative / absolute path we are dealing with I have absolutely no experience with e.g. docker

            – KJO
            25 mins ago











          • I mean that possibly adding newcommandcommonpath/home/<username>/Common could solve the problem and you don't have to be specific here... Just shared the idea... But again.. I didn't understood the problem in the question yet. (I just think that some answer similar to any answer of this tex.stackexchange.com/q/1137/120578 could be a possible answer as far as I can understand the question)

            – koleygr
            17 mins ago






          • 1





            @koleygr I agree for sty files there are many answers but xindy has its own variables and AFAIK glossaries as built at compilation time by the tex file cannot be easily collated from a central location, but I have not tried out glossaries enough to do otherwise :-)

            – KJO
            9 mins ago






          • 1





            Thanks... didn't noticed that... Actually I don't have the needed experience with glossaries too.

            – koleygr
            4 mins ago
















          +1 for helping him/her after so much time... But adding also a way as an example like using a non-relative but an absolute path would make your question better and reviewers would not recommend deletion in any case ;) (But I haven't really understood the question enough)

          – koleygr
          28 mins ago






          +1 for helping him/her after so much time... But adding also a way as an example like using a non-relative but an absolute path would make your question better and reviewers would not recommend deletion in any case ;) (But I haven't really understood the question enough)

          – koleygr
          28 mins ago














          @koleygr I am trying not to ask in 20 different comments what type of relative / absolute path we are dealing with I have absolutely no experience with e.g. docker

          – KJO
          25 mins ago





          @koleygr I am trying not to ask in 20 different comments what type of relative / absolute path we are dealing with I have absolutely no experience with e.g. docker

          – KJO
          25 mins ago













          I mean that possibly adding newcommandcommonpath/home/<username>/Common could solve the problem and you don't have to be specific here... Just shared the idea... But again.. I didn't understood the problem in the question yet. (I just think that some answer similar to any answer of this tex.stackexchange.com/q/1137/120578 could be a possible answer as far as I can understand the question)

          – koleygr
          17 mins ago





          I mean that possibly adding newcommandcommonpath/home/<username>/Common could solve the problem and you don't have to be specific here... Just shared the idea... But again.. I didn't understood the problem in the question yet. (I just think that some answer similar to any answer of this tex.stackexchange.com/q/1137/120578 could be a possible answer as far as I can understand the question)

          – koleygr
          17 mins ago




          1




          1





          @koleygr I agree for sty files there are many answers but xindy has its own variables and AFAIK glossaries as built at compilation time by the tex file cannot be easily collated from a central location, but I have not tried out glossaries enough to do otherwise :-)

          – KJO
          9 mins ago





          @koleygr I agree for sty files there are many answers but xindy has its own variables and AFAIK glossaries as built at compilation time by the tex file cannot be easily collated from a central location, but I have not tried out glossaries enough to do otherwise :-)

          – KJO
          9 mins ago




          1




          1





          Thanks... didn't noticed that... Actually I don't have the needed experience with glossaries too.

          – koleygr
          4 mins ago





          Thanks... didn't noticed that... Actually I don't have the needed experience with glossaries too.

          – koleygr
          4 mins ago

















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f479841%2fmake-tex-glossaries-files-accessible-for-all-documents-across-system%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

          How should I use the fbox command correctly to avoid producing a Bad Box message?How to put a long piece of text in a box?How to specify height and width of fboxIs there an arrayrulecolor-like command to change the rule color of fbox?What is the command to highlight bad boxes in pdf?Why does fbox sometimes place the box *over* the graphic image?how to put the text in the boxHow to create command for a box where text inside the box can automatically adjust?how can I make an fbox like command with certain color, shape and width of border?how to use fbox in align modeFbox increase the spacing between the box and it content (inner margin)how to change the box height of an equationWhat is the use of the hbox in a newcommand command?

          Doxepinum Nexus interni Notae | Tabula navigationis3158DB01142WHOa682390"Structural Analysis of the Histamine H1 Receptor""Transdermal and Topical Drug Administration in the Treatment of Pain""Antidepressants as antipruritic agents: A review"

          inputenc: Unicode character … not set up for use with LaTeX The Next CEO of Stack OverflowEntering Unicode characters in LaTeXHow to solve the `Package inputenc Error: Unicode char not set up for use with LaTeX` problem?solve “Unicode char is not set up for use with LaTeX” without special handling of every new interesting UTF-8 characterPackage inputenc Error: Unicode character ² (U+B2)(inputenc) not set up for use with LaTeX. acroI2C[I²C]package inputenc error unicode char (u + 190) not set up for use with latexPackage inputenc Error: Unicode char u8:′ not set up for use with LaTeX. 3′inputenc Error: Unicode char u8: not set up for use with LaTeX with G-BriefPackage Inputenc Error: Unicode char u8: not set up for use with LaTeXPackage inputenc Error: Unicode char ́ (U+301)(inputenc) not set up for use with LaTeX. includePackage inputenc Error: Unicode char ̂ (U+302)(inputenc) not set up for use with LaTeX. … $widehatleft (OA,AA' right )$Package inputenc Error: Unicode char â„¡ (U+2121)(inputenc) not set up for use with LaTeX. printbibliography[heading=bibintoc]Package inputenc Error: Unicode char − (U+2212)(inputenc) not set up for use with LaTeXPackage inputenc Error: Unicode character α (U+3B1) not set up for use with LaTeXPackage inputenc Error: Unicode characterError: ! Package inputenc Error: Unicode char ⊘ (U+2298)(inputenc) not set up for use with LaTeX