![](img/logo2.gif) Website founded by Milan Velimirović in 2006
1:37 UTC
![59th WCCC](img/logo3.png)
![Donate MatPlus](img/donate_PNG13.png)
| |
MatPlus.Net Forum Internet and Computing Olive Format Specification? |
|
|
|
You can only view this page!
| | (1) Posted by Hauke Reddmann [Friday, Nov 5, 2021 16:42] | Olive Format Specification? I'm migrating my problem collection to Olive. Since I already have
a ton of HTML, I copypaste directly into *.olv which is plaintext
(thank your favorite deity).
Some remarks:
- Tags are randomly in [],' or none, and it even varies between
problems. Can you give me the exact specification?
- h#2 is the default.* Is it safe to edit in + (Popeye of course
doesn't solve e.g.) as goal in a olv file? (So far only the Popeye solver
objects - which I can simply ignore - but not Olive.)
- Some special characters seem to have special use. Which must
I exclude/escape from, say, comments?
- Fonts mention "ches", where do I get it (not that I really need it)?
* Obviously I want Hauke-Olive for #2 default :-) | | (2) Posted by Dmitri Turevski [Friday, Nov 5, 2021 17:26] |
QUOTE Tags are randomly in [],' or none, and it even varies between problems. Can you give me the exact specification?
Same as the YACPDB entry format for the most recent version.
https://github.com/dturevski/olive-gui/blob/master/yacpdb/schemas/yacpdb-entry.md
It's YAML based, see the YAML documentation, it allows some variability in defining complex objects (thus seemingly random use of brackets).
QUOTE Is it safe to edit in + (Popeye of course doesn't solve e.g.) as goal in a olv file?
Should be pretty safe, bar the popeye issue.
QUOTE Some special characters seem to have special use. Which must I exclude/escape from, say, comments
Should be compatible with the YAML methods of escaping.
QUOTE Fonts mention "ches", where do I get it (not that I really need it)?
https://yacpdb.org/misc/fonts/CHES.TTF
QUOTE Obviously I want Hauke-Olive for #2 default
"File -> Save template" saves the current entry as a template for the new entries. So by changing the stipulation of a blank entry to #2 and doing the "File -> Save template" the "#2" would become new default. Protip: the stipulation may not be the only default value that you may want to temporary redefine: non blank authors, source, date are also handy sometimes. | | (3) Posted by Hauke Reddmann [Saturday, Nov 6, 2021 10:03] | THX for the quick and protip answer! I recognize a computer
profi when I see one :-)
(At the moment defaulting to my name is a nonfeature since
I am writing a Python script to convert my HTML pages to
.olv and insert it directly, but this will come very handy
for the long overdue update of my problem collection...
after that.) | | (4) Posted by Hauke Reddmann [Saturday, Nov 6, 2021 17:56] | @Dmitri: Another two questions, one regarding nested tags and one for CHES.
source:
name: The Cook
issue: 3
problemid: 1
date:
year: 1975
month: 9
(Think indents.)
In RTF, this ends up as bracket salad (I'd prefer
"The Cook, issue 3, #1, 1975/9" or suchlike.
Does that only work if just source and date are set
non-nestedly? Your YAML example ends up in {} either...
If I want to edit the font (say with glyphs for G and N),
does Ches recognize the new glyphs in solutions and
which glyph (and possibly glyph names?) must I edit?
(Ches has renamed glyphs!) | | (5) Posted by Dmitri Turevski [Saturday, Nov 6, 2021 20:05] |
QUOTE Does that only work if just source and date are set non-nestedly?
To change how the details are rendered in RTF/PDF you can modify the Olive source code - it's a Python 3 script available at github. In a sense it is a much better approach than stuffing the source field with date and other details. User templates are not supported at the moment (the task is not straighforward, multi-language nature of Olive should be taken into the consideration).
QUOTE If I want to edit the font (say with glyphs for G and N), does Ches recognize the new glyphs in solutions and which glyph (and possibly glyph names?) must I edit?
This is probably doable, but is much trickier. First, ches.ttf doesn't contain glyphs for nightrider and grasshopper, so indeed the graphics file should be modified (and it is likely to be restrictively copyrighted and support should be dropped from Olive in the first place). Second, non-orthodox glyphs in the solution were never planned, so the code modifications would require deeper changes in the Olive inner works.
I feel like this discussion belongs to the Olive's issues/request page - feel free to post there:
https://github.com/dturevski/olive-gui/issues | | (6) Posted by Hauke Reddmann [Sunday, Nov 7, 2021 09:28] | I don't know why I hate GIT, but I just got a new reason:
"Hey, we don't let any git in. First verify your device.
We sent a verification mail to your email address. Which
is long obsolete, as email addresses are prone to. Why didn't
you change it like on all the other 239 sites you had to
change when your account ran out? You forgot? Luser."
But since this is very OT for MPF, I will carry *that*
issues to the GIT-lovers at my university :-) | | No more posts |
MatPlus.Net Forum Internet and Computing Olive Format Specification? |
|
|
|