Thoughts about support for multiple (human) languages #254
Replies: 4 comments 11 replies
-
Code looks pretty decent already! Sweet! Some initial thoughts and replies.
|
Beta Was this translation helpful? Give feedback.
-
According to the specification, the My commit thorehusfeldt@84fdb98 introduces the attribute (human)
Instead, there should be |
Beta Was this translation helpful? Give feedback.
-
I would suggest to make
|
Beta Was this translation helpful? Give feedback.
-
The question is how
|
Beta Was this translation helpful? Give feedback.
-
The commit thorehusfeldt@84fdb98 is a first attempt to support other languages than English.
Currently it allows
to turn
problem_statement/problem.da.tex
intoproblem.pdf
, including reading the Danish problem name fromproblem.yaml
according to the specification, seeThe next steps require some thought:
nl
contest gracefully fall back toen
for problem D if thenl
statement is not available? (I think yes.) There are lots of extra contest-related files and infrastructure that I honestly don’t yet understand.problem.da.pdf
etc? I like this. It could also allowbt pdf --all
or something like that. (Or havebt pdf
produce all languages it can find by default.) Opinions are welcome.solution.tex
is not ready for this. The obvious solution is to expectsolution.nl.tex
(withsolution.tex
as an alias forsolution.en.tex
)problem_default_language
be introduced and be configurable (instead hardcoding a preference foren
)? I think it’s not worth doing.problem_statement
? This is a minor issue because it only applies to PDF printouts and typically isn’t moved to the judging platform anyway. I think it’s not worth doing.Beta Was this translation helpful? Give feedback.
All reactions