Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

organize post-processing in a maintainable way #11

Open
S6savahd opened this issue Jun 20, 2016 · 2 comments
Open

organize post-processing in a maintainable way #11

S6savahd opened this issue Jun 20, 2016 · 2 comments

Comments

@S6savahd
Copy link

S6savahd commented Jun 20, 2016

for each volume, we will have 0-3 things that the fully automated case gets wrong.
For these, we need hard-coded post-processing rules and these rules should be in a place where it is easy to maintain them.
For example, we do not want 100s of lines of volume specific text distinctions in serializer.py.
(maybe with a subdirectory of files with Python modules).

@S6savahd
Copy link
Author

S6savahd commented Jul 1, 2016

it is good in its current status but since this is a longterm issue, we keep it open.

@liyakun
Copy link

liyakun commented Jul 30, 2016

changed all previous text processing by using triple.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants