lugrim/seri

A way too much over-engineered timetable language compiler

seri's Issues

Write language specification

Parse description as markdown

To be able to format descriptions / abstracts, we should parse them as markdown

Manage key not found in templating

          What would happen if the key is not found in the template ? Can we raise a `TemplateKeyNotFound` error in `templating.rs`

Originally posted by @hugnata in #22 (comment)

For now, it doesn't do anything, we may want to raise an error

Switch to tectonic instead of latexmk ?

Name convention

We should find a way to distinguish between "event" meaning "the whole thing the calendar is for" and "a single talk/meal/activity"

`-s` does nothing on passes involving latexmk

When present, behaves as it should.
When absent, the program hangs.

How about a language field in the seri description ?

Since not everyone is comfortable about giving a talk of english, should we add a field to the seri language to define the language of a talk ? Similarly to the speakers attribute, the lang attribute would be useful only for talks.

Any opinion on this ?

Add Seminar title

Maybe in some global metadata or CLI option ?

Add some helper functions to bounding box

          We could maybe add, in future development, helper functions like:

• number_of_days(&self) -> u32 -> Return the number of days the event will last
• time_window_hour(&self) -> (u32, u32) -> Return a tuple containing the maximal time window the event will span over = (self.up_left.hour, self.down_right.hour)

Originally posted by @hugnata in #15 (comment)

♻️ Refactor: create traits `ToTikz` and `ToLatex`

This refactoring would help to produce better code

tikz compilation application is too long

The method apply in the implementation of CompilationPass for TikzBackend is way too long and tries to create the whole latex code in one block. It would be a good thing to separate the different steps into smaller functions. I did it for speaker_string, but more functions are welcome.

As a first step, it would be nice to add comments in the function to split it into the logical steps. Then, multiple contributors will split it at will. I personally don't understand the big function very well due to its length and gory format.

Bottom-right bound inherits month and year, but not top-left one

When building the BoundingBox of events, it appears at latex.rs:77 that the bottom-right bound of the box inherits the month and year of the bottomest-rightest date, but the same operation does not happen when building the top-left bound at latex.rs:66.

Why is it like this? Is it normal?