The grid doesn't work with eso-pic after version 2.0. The actual version was based on the eso-pic version 1.1 where it still works, but i haven't found the difference in the package (might also depend on the change there from everyshi to atbegshi).

Any ideas appreciated

When using the hyperref package, kartei won't work in print mode and instead will only output every other card as if it was running in preview mode. To reproduce, add \usepackage{hyperref} to beispiel.tex right before the document begins.

I'm not sure whether it makes sense to use hyperref with kartei at all, but it's being included in my default template and hence I noticed this bug.

Bei a7paper überschneiden sich die Ränder der Karten:
debug.pdf

\documentclass[a7paper,11pt,print,grid=both]{kartei}

\usepackage[utf8]{inputenc} %UTF8
\usepackage{amssymb}
\usepackage{amsmath}

\begin{document}
\section*{Strategic Games}
\begin{karte}{Normal form game}
\ldots is a tupel $(\mathcal{N}, (S_i)_{i\in N}, (c_i)_{i\in N})$ where
\end{karte}

\begin{karte}{Dominant strategy}
\ldots for player $i$ is a strategy $s\in S_i$ with
\[
	c_i(s_i, s_{-i}) \leq c_i(s'_i, s_{-i}) \quad \forall s'_i \in S_i, s_{-i}\in S_{-i}
\]
\end{karte}
\begin{karte}{Dominant strategy}
\ldots for player $i$ is a strategy $s\in S_i$ with
\[
	c_i(s_i, s_{-i}) \leq c_i(s'_i, s_{-i}) \quad \forall s'_i \in S_i, s_{-i}\in S_{-i}
\]
\end{karte}
\end{document}

Ich benutze kartei von commit 5368e8b mit
scrpage2 [2020/02/27 v3.30 unsupported obsolete former KOMA-Script package] und

$ pdflatex --version
pdfTeX 3.141592653-2.6-1.40.25 (TeX Live 2023/Arch Linux)
kpathsea version 6.3.5
Copyright 2023 Han The Thanh (pdfTeX) et al.
There is NO warranty.  Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Han The Thanh (pdfTeX) et al.
Compiled with libpng 1.6.39; using libpng 1.6.39
Compiled with zlib 1.2.13; using zlib 1.2.13
Compiled with xpdf version 4.04

First: It's a great package and helps me A LOT! Thanks for all the work that went in it.

I tried printing cards with it and noticed, that almost no laser printer is capable of printing margin-free. Also I'd accept smaller cards, as long as they were equally sized. Hence my feature suggestion:

Add a parameter, that allows page margins to be specified as well as the grid size (e.g. 2x4). Then layout the specified page grid into the printable area. After printing you will have to cut all cards on all sides and the cards will be smaller, but you end up with equally sized, fully printed cards.

I don't know enough latex to create that feature myself, but it would help.

One enhancement to the Kartei-Package would be to implement an additional page (A4 independent of the cards or the print mode) that lists all cards.

This could be done as a simple List (perhaps using makeidx) or as a tabular, which would enable the list to have columns for „card learned“ and stuff like that. Either way, collecting card title + card numer isn't that easy, hence any idea is welcome.

After successfully using your package for over a year, I was going back to an old project of mine and tried compiling it.
This is the result:

This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) (preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./tgi-lernkarten-master.tex
LaTeX2e <2020-10-01> patch level 4
L3 programming layer <2021-01-09> xparse <2020-03-03> (./kartei.cls
Document Class: kartei 2011/12/31 Karteikarten in LaTeX, Version 1.8b2
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrartcl.cls
Document Class: scrartcl 2020/09/21 v3.32 KOMA-Script document class (article)
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrkbase.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrbase.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile-hook.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlogo.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/tocbasic.sty)
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrsize12pt.clo)
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/typearea.sty
DIV calculation for typearea with good linewidth.
))

! LaTeX Error: File `scrpage2.sty' not found.

Type X to quit or <RETURN> to proceed,
or enter new name. (Default extension: sty)

Enter file name: 
./kartei.cls:134: Emergency stop.
<read *> 
         
l.134 \RequirePackage
                     {xargs}^^M
./kartei.cls:134:  ==> Fatal error occurred, no output PDF file produced!
Transcript written on ../tgi-lernkarten-master.log.

I am using Debian GNU/Linux 11.

Reading this StackExchange answer suggests simply replacing scrpage2 with scrlayer-scrpage in the file kartei.cls should work, and it does indeed work.

Thanks for looking into this.

As most of the files are not used very often by the user, I propose to put them into a separate folder like this:

├── Kartei
│   ├── kartei.a5printstyle.tex
│   ├── kartei.a5printstylerotation.tex
│   ├── kartei.a6printstyle.tex
│   ├── kartei.a6printstylerotation.tex
│   ├── kartei.a7printstyle.tex
│   ├── kartei.a7printstylerotation.tex
│   ├── kartei.a8printstyle.tex
│   ├── kartei.a8printstylerotation.tex
│   ├── kartei.a9printstyle.tex
│   ├── kartei.a9printstylerotation.tex
│   ├── kartei.cls
│   ├── kartei.pageshipout.tex
│   ├── kartei.print.tex
│   ├── kartei.tableofcontents.tex
│   └── texput.log
├── Readme.md
├── beispiel.pdf
├── beispiel.tex
├── manual.pdf
├── manual.tex
├── manualexample1.pdf
└── manualexample1.tex

This is how the files are currently structured in my develop branch (unfortunately with some other things as well, as I am new to git and made a mess).

kartei.cls works well on Texlive/Linux but fails on Windows/MikTex due to outdated and thus no longer existent scrpage2 package, see https://tex.stackexchange.com/questions/541766/latex-error-file-scrpage2-sty-not-found for further reference.

I manually used the proposed replacement of \usepackage[headsepline]{scrpage2} by \usepackage[headsepline]{scrlayer-scrpage} in kartei.cls. This kind of works but the cards' header texts then intersect with the separation lines.

Hi,

I found your package while looking for a LaTeX package for flashcards, and so far, it seems like exactly the sort of thing I was looking for.

I would like to help by translating as much of the instructions, etc. as I can into English – so perhaps it can become accessible to a wider audience.

Firstly, would you be interested a pull request for such a translation? I have an example translation of the first page of the manual in my fork. Your project page does mention Instructions in English.

If the answer to the above is yes, what do you think would be the best way to go about doing this? I can see a few options:

1. Retain single files (e.g. README.md, manual.pdf, and just have sections of German and English text in each.

2. Have separate files for English and German README.md, README-en.md, manual-en.pdf, etc. (This is the approach I am currently taking in my repo).

3. Simply maintain a different branch in Git for the English translation, and (I'm not quite sure how this would work) generate -en releases from it or something.

4. Something else?

Anyway, let me know what you think!

As long as you retainthis notice you can do whatever

Shouldn't this be "As long as you retain this notice you can do whatever"

While I'm at it, another feature request:

Provide an option to shuffle the cards in a way, that they will come out correctly if cut en mass. Define a cutting procedure like

• Hold in landscape mode
• Cut vertical
• Put left on top of right
• Rotate 90 degree to the right
• Repeat

When doing this, the order of the cards will be shuffled. Hence it would help to order the cards in a way, that will make them come out of said cutting procedure in a ordered fashion.

This is highly optional, but it came to my mind so I though I could share it as well.

Hallo,

Eine Erweiterung in den Karteikarten sehe ich in der Möglichkeit die Vorderseite identisch zur Rückseite zu formatieren. Damit lassen sich Aufgaben stellen, die direkt auf der Seite bearbeitet werden können. Hierzu habe ich ein Beispiel angehängt. Für das angehängte Beispiel habe ich in den Dateien des Karteikarten-Sets rumgefuscht... ich weiß aber nicht mehr, wo ich die Änderung vorgenommen habe.

Im gleichen Zug würde empfehlen den Bereich der Vorder- und Rückseite ganz leicht zu verändern und mehr Platz für ein \rofoot{} in Kartei.cls zu erlauben. In dieser zusätzlichen Fußzeile kann man dann bspw. "Version" oder "Autor" reinschreiben. Elemente, die auf jeden Fall über alle Seiten gleich bleiben. Falls dies nicht in Frage kommt... mag mir jemand sagen, wie ich welche Datei dafür modifiziere? :-)

ANALYSIS II - Karteikarten_v1.01_split_1.pdf

Danke! Und überhaupt - tolle Karteikatenvorlage. Habe für Analysis II 170 Karteikarten erstellt :-)

BG, Bernd

I want to install this "packages" but I dont like to be in the same folder to create my flashcards. I'm using orgmode so this would be a real mess to deal with. How do I install on my pc so I dont need to care about these files anymore? I read something about texthash but I'm unsure how to use it.

It would come in very handy to print out all questions and answers next to each other.

The deluxe version would surely be some sort of definition list, but just two columns of A7 cards, on the left side the front, and on the right side the backside of the same card, and hence 4 cards on one A4 sheet would also be sufficient.

Is there a way to specify the padding of each card? Possibly even per side? I think the padding on the right side is a bit too small, especially in print-mode.

This is not a duplicate of #4.

Example with the distances marked:

Since I want to write chinese learning cards I need to use the xelatex compiler in order to use the package xeCJK.
However, e.g. using the option a8paper or a4paper together with "print" the output of the first page seems buggy.