You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- For collecting classified content in large quantities which you can then select, group and assemble into different documents, I think a database is indeed the best solution. For customising section titles and such, probably TeX macro names which can be configured by a document class or package are a better choice (analogously to the key words "Table of Contents" or "Abstract" used by LaTeX).Stephan Lehmke– Stephan Lehmke2012-06-30 09:44:17 +00:00Commented Jun 30, 2012 at 9:44
- @StephanLehmke Excellent. Thanks. Then my question is just: what is the most efficient way to do this. Is there some LaTeX package that can grab data from a (certain) database?Jonas T– Jonas T2012-06-30 09:56:33 +00:00Commented Jun 30, 2012 at 9:56
- Maybe the answers to this question can help? Is it possible to connect a database to LaTeX to produce data-driven documents?Stephan Lehmke– Stephan Lehmke2012-06-30 12:29:19 +00:00Commented Jun 30, 2012 at 12:29
- @StephanLehmke Thanks. All these solutions are "too big", I mean, then it would be better to write a script that spits out these things. The problem is that I also want to compile these files through LaTeX to see how they look and, putting them in an XML file is not going to make that much easier. So perhaps the macro names can solve this. The problem is that I also might want to change the order... Good old copy pasting does the trick, but I'd like something more usable.Jonas T– Jonas T2012-07-03 00:35:03 +00:00Commented Jul 3, 2012 at 0:35
- Writing a simple script from scratch which will spit out some LaTeX source is a perfectly good solution in my opinion. Every relevant programming language has some facilities for accessing databases, and generating the LaTeX code is mostly a matter of printing some text to a file. I doubt you'll be having much trouble with this.Stephan Lehmke– Stephan Lehmke2012-07-03 06:32:35 +00:00Commented Jul 3, 2012 at 6:32
| Show 1 more comment
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. tikz-pgf), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-tex