132 lines
3.3 KiB
Markdown
132 lines
3.3 KiB
Markdown
# TODO:
|
|
|
|
- [ ] test with example5.tex
|
|
- [ ] make tex parser cleaner and think more about structure of entries and levels
|
|
- [ ] what about root of a word?
|
|
- [ ] [conlang lexicon](https://github.com/CodeTriangle/Perplexicon/)
|
|
- [ ] [word net schemas](https://globalwordnet.github.io/schemas/)
|
|
- [ ] [dict.cc word lists](https://www1.dict.cc/translation_file_request.php)
|
|
- [ ] [moby (thesaurus](https://github.com/words/moby/)
|
|
- [ ] [english-hebrew lexicon](https://github.com/eliranwong/unabridged-BDB-Hebrew-lexicon)
|
|
- [ ] how should the output of texdict.py -o tex be used?
|
|
```
|
|
\documenttype{standalone}
|
|
%\usepackage{texdict}
|
|
\begin{document}
|
|
\input{output-from-textdict.tex}
|
|
\end{document}
|
|
```
|
|
- [ ] if dict package, how can I keep texdict.py and texdict.sty in sync?
|
|
- [ ] textdict.py needs to be part of textdict.sty package
|
|
|
|
- [ ] refactor code acording to 12factor app
|
|
- [ ] https://12factor.net/de/
|
|
- [ ] what about that every entry should only appear once?
|
|
- [ ] if input and output are the same, should it be converted to json trotzdem?
|
|
- [ ] maybe not and add a --test flag for testing the syntax correctness
|
|
- [ ] logo could be
|
|
```
|
|
\documentclass{standalone}
|
|
\begin{document}
|
|
$\tau$e$\chi$\textit{dict}\texttt{.py}
|
|
\end{document}
|
|
```
|
|
|
|
- [ ] are there similar programs? json dictionary/lexicon data formats?
|
|
- [ ] are there better latex packages (than glossaries) to build on?
|
|
|
|
|
|
---
|
|
---
|
|
|
|
- [x] test:
|
|
- [x] $(./texdict.py example2.json -o tex`)
|
|
- [x] dann auch testen:
|
|
- [x] $(./texdict.py example2.tex )
|
|
|
|
|
|
|
|
|
|
|
|
- [x] change such that two entries can be converted
|
|
- [x] json:
|
|
```
|
|
{[entry1,e2,e3]}
|
|
{entries : [entry1, entry2, entry3]}
|
|
```
|
|
- [x] tex
|
|
```
|
|
\entry{1}
|
|
\entry{2}
|
|
\entry{3}
|
|
```
|
|
|
|
|
|
\documentclass{standalone}
|
|
\begin{document}
|
|
$\tau$e$\Xi$\textit{dict}\texttt{.py}
|
|
\end{document}
|
|
|
|
|
|
|
|
a poems with vim
|
|
a poems with him
|
|
|
|
a poems with vim vim
|
|
a poems with vim vim
|
|
|
|
---
|
|
example.json
|
|
```
|
|
{
|
|
"entries": [
|
|
{
|
|
"entry": "asɛm",
|
|
"key": "as3m",
|
|
"meanings": [
|
|
{
|
|
"type": "noun",
|
|
"description": "word",
|
|
"examples": [
|
|
"Wonim saa asɛm yi?",
|
|
" Wo nim sa ara asɛm yi? "
|
|
]
|
|
}
|
|
]
|
|
}
|
|
]
|
|
}
|
|
```
|
|
\glossary{entry}{key}{
|
|
\m (type) description, description, description ; example, example
|
|
\m
|
|
}
|
|
- tex2json
|
|
```
|
|
def tex2json(dict_tex)
|
|
meaning_delim='\m '
|
|
type_delim=['(',') ']
|
|
description_delim=', '
|
|
examples_delim='; '
|
|
example_delim=', '
|
|
# how to cope with multiline entries?
|
|
- [find closing brackets](https://stackoverflow.com/q/63382152)
|
|
```
|
|
- notes:
|
|
- `type` could also include gender/genus?
|
|
- where should I put info like 'go, went, gone' or plural forms for some words?
|
|
- `grammar`: with additional usage info?
|
|
- `root` could be included in `etymology` oder `origin`?
|
|
- `dialect/usage/gebrauch`
|
|
- https://www.duden.de/hilfe/gebrauch
|
|
- statt `description` = `meaning`?
|
|
- what about `see also`s and confere (cf.)
|
|
- what about `aussprache`?
|
|
|
|
```
|
|
\glossary{entry}{key}{
|
|
\m (type) description, description, description ; example, example
|
|
\m
|
|
}
|
|
- tex2json
|