lnum wise entry for data in csl-devanagari for Devanagari correction submission.
1
stars
9
forks
source link
readme
Data organization
Data is arranged in the following manner in the directory. csl-ldev/v02/dictcode/ldev.txt. e.g. csl-ldev/v02/snp/35.txt will give you dictionary entry corresponding to ldev 35 in snp dictionary.
This serves the purpose that this file can be directly linked from display or stardict files. If anyone finds some error, he can submit the error or pull request here.
Scripts
txt_to_ldev.py - This script generates ldev wise entries from given dictcode. e.g. python3 txt_to_ldev.py mw will generate ldev wise entries in the csl-ldev/v02/mw repository.
redo_all.sh - This script will regenerate all dictionaries based on latest data at csl-devanagari repository. bash redo_all.sh.
ldev_to_csldevanagari.py - This script takes two arguments dictId and lnum. This script is used to carry the changes made in csl-lnum repository by a user to csl-devanagari repository. Usage - python3 ldev_to_csldevanagari.py skd 15140 will take the file csl-ldev/v02/skd/15140.txt and integrate that data to csl-devanagari/v02/skd/skd.txt.
After the changes are transferred to csl-devanagari repository, go to csl-devanagari/scripts/ and transfer the changes by python3 to_slp1.py dictId and cp ../slp1/$dict.txt ../../csl-orig/v02/dictId/dicdId.txt. This would transfer the changes from csl-devanagari to csl-orig (original data of Cologne).
Danger
Do not do git status on this repository in CLI. It will take a lot of time to make index of 12-15 lacs files in this repository and git will kill your computer.
You should do git add changed file directly and proceed.