Kdtyjb

Is it insecure to send a password in a `curl` command?

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

Can I use USB data pins as power source

Math equation in non italic font

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

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

Happy pi day, everyone!

What is a ^ b and (a & b) << 1?

How to pronounce "I ♥ Huckabees"?

Why is the President allowed to veto a cancellation of emergency powers?

The German vowel “a” changes to the English “i”

What are substitutions for coconut in curry?

Is there a hypothetical scenario that would make Earth uninhabitable for humans, but not for (the majority of) other animals?

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

How are passwords stolen from companies if they only store hashes?

What is the significance behind "40 days" that often appears in the Bible?

Are all passive ability checks floors for active ability checks?

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?

Most cost effective thermostat setting: consistent temperature vs. lowest temperature possible

Problem with FindRoot

Why one should not leave fingerprints on bulbs and plugs?

Why no Iridium-level flares from other satellites?

Print a physical multiplication table

Examples of transfinite towers

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 producedCan't create glossary with glossaries package,Perl Strawberry, error: makeglossaries:Need exactly one file argumentMikTeX Deployment for multiple usersLaTeX 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

newcommand{commonpath}{../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

edited 4 mins ago

KJO

3,0681120

asked 4 hours ago

krtekkrtek

890820

add a comment | 

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

newcommand{commonpath}{../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

edited 4 mins ago

KJO

3,0681120

asked 4 hours ago

krtekkrtek

890820

add a comment | 

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

newcommand{commonpath}{../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

edited 4 mins ago

KJO

3,0681120

asked 4 hours ago

krtekkrtek

890820

newcommand{commonpath}{../Common}

share|improve this question

edited 4 mins ago

KJO

3,0681120

asked 4 hours ago

krtekkrtek

890820

share|improve this question

edited 4 mins ago

KJO

3,0681120

asked 4 hours ago

krtekkrtek

890820

edited 4 mins ago

KJO

3,0681120

edited 4 mins ago

KJO

3,0681120

asked 4 hours ago

krtekkrtek

890820

asked 4 hours ago

krtekkrtek

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

edited 28 mins ago

answered 36 mins ago

KJOKJO

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
  27 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
  24 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I mean that possibly adding newcommand{commonpath}{/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
  16 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
  8 mins ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Thanks... didn't noticed that... Actually I don't have the needed experience with glossaries too.
  
  – koleygr
  3 mins ago
  

  
  
  
  

add a comment | 

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

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

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

Name

Email

Required, but never shown

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

edited 28 mins ago

answered 36 mins ago

KJOKJO

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
  27 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
  24 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I mean that possibly adding newcommand{commonpath}{/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
  16 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
  8 mins ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Thanks... didn't noticed that... Actually I don't have the needed experience with glossaries too.
  
  – koleygr
  3 mins ago
  

  
  
  
  

add a comment | 

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

edited 28 mins ago

answered 36 mins ago

KJOKJO

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
  27 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
  24 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I mean that possibly adding newcommand{commonpath}{/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
  16 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
  8 mins ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Thanks... didn't noticed that... Actually I don't have the needed experience with glossaries too.
  
  – koleygr
  3 mins ago
  

  
  
  
  

add a comment | 

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

edited 28 mins ago

answered 36 mins ago

KJOKJO

3,0681120

share|improve this answer

edited 28 mins ago

answered 36 mins ago

KJOKJO

3,0681120

answered 36 mins ago

KJOKJO

3,0681120

answered 36 mins ago

KJOKJO

3,0681120