## Where communities thrive

• Join over 1.5M+ people
• Join over 100K+ communities
• Free without limits
##### Activity
• Dec 05 15:30
renovate[bot] edited #1109
• Dec 05 15:30

epage on master

chore(ci): Update renovate (compare)

• Dec 02 04:51

renovate[bot] on concolor-clap-0.x

• Dec 02 04:51
renovate[bot] closed #1112
• Dec 02 04:51
renovate[bot] edited #1112
• Dec 02 04:51

renovate[bot] on concolor-0.x

• Dec 02 04:51
renovate[bot] closed #1111
• Dec 02 04:51
renovate[bot] edited #1111
• Dec 02 01:22

epage on master

• Dec 02 01:17
renovate[bot] synchronize #1112
• Dec 02 01:17

renovate[bot] on concolor-clap-0.x

chore(deps): update rust crate … (compare)

• Dec 02 01:13

epage on master

chore(deps): update safe Merge pull request #1105 from c… (compare)

• Dec 02 01:13

epage on safe

• Dec 02 01:13
epage closed #1105
• Dec 01 22:31
renovate[bot] synchronize #1105
• Dec 01 22:31

renovate[bot] on safe

chore(deps): update safe (compare)

• Dec 01 22:22
renovate[bot] synchronize #1105
• Dec 01 22:22

renovate[bot] on safe

chore(deps): update safe (compare)

• Dec 01 22:17

epage on env_logger-0.x

• Dec 01 22:17

epage on master

chore(deps): update rust crate … Merge pull request #1106 from c… (compare)

[m]
I don't think so. It uses the excerpt, afaik… Perhaps you can adjust the excerpt to default to the entire content somehow? Adjusting default.excerpt_separator in _cobalt.yml might work.
Tassilo Horn
@tsdh
fantasycookie17:artemislena.eu: Yeah, that seems to do the trick! Thanks.
[m]
Out of curiosity, what value did you set it to?
Tassilo Horn
@tsdh
self-documenting values are even better than comments.
[m]
Ah, alright. I'm not too aware of how Cobalt works internally, so didn't know whether not finding the excerpt separator might lead to it being empty.
Ed Page
@epage
A marker for what leading content should be extracted from the content as an excerpt. "" will cause no excerpt to be generated.
https://cobalt-org.github.io/docs/front/
When there is no excerpt, we use the full content
Tassilo Horn
@tsdh
Indeed, that also works. Thanks, epage.
Tassilo Horn
@tsdh
I have in a markdown listing the text: <description>{{ .Summary | html }}</description>
Now cobalt seems to try to interpret that. At least "cobalt serve --drafts" errors like shown here: https://paste.sr.ht/~tsdh/e8d899adc04844c4b558f9db21895e31b68cb72c
I'd expect that listings aren't processed but taken verbatim. Is there something I can do about it?
Ed Page
@epage
What do you mean by "listing"?
Tassilo Horn
@tsdh
epage: I mean markdown's \n...\n construct.
Or language\n...\n
Ed Page
@epage
Liquid has no knowledge of markdown and gets processed first
You'll need {{ raw }} for that
Tassilo Horn
@tsdh
epage: You mean surround the ... with {% raw %} ... {% endraw %}?
Tassilo Horn
@tsdh
epage: That did the trick.
Newbyte
@newbyte:matrix.org
[m]
👋
Ed Page
@epage
Greetings! @newbyte:matrix.org !
Newbyte
@newbyte:matrix.org
[m]
Is it possible to insert equations into Cobalt posts? Preferably with LaTeX syntax.
Ed Page
@epage
Natively? Not yet. We have an issue for cobalt-org/cobalt.rs#280 though I'm not particular about what style we support.
Newbyte
@newbyte:matrix.org
[m]
Thanks!
Newbyte
@newbyte:matrix.org
[m]
Is there any documentation about how to use the scss support in Cobalt?
Ed Page
@epage

Little direct documentation: https://cobalt-org.github.io/docs/assets/

You can choose our CSS is rendered: https://cobalt-org.github.io/docs/config/

You have the _sass directory for files you can import: https://cobalt-org.github.io/docs/directory/

Other than that, it should just be a matter of having the files on disk and they should get processed

3 replies
Newbyte
@newbyte:matrix.org
[m]
(the one generated by the sass compiler)
David J. Weller-Fahy
@djwf
@epage - with_time is only ever going to be used in our tests, right?
Ed Page
@epage
Yes, its just exposed in the test helpers
David J. Weller-Fahy
@djwf
ok, I believe I've figured out how to make it work, then
David J. Weller-Fahy
@djwf
although I believe our DateTime implementation will need some tweaking in terms of what it accepts - our implementation should be able to handle PrimitiveDateTime (no offset), but right now it only accepts OffsetDateTime. Ideally, it should handle any single date, time, and datetime with or without offset. So I'm going to fiddle with our DateTime to get it to that point, and then fix with_time. Sound good?
Note that when I'm talking about PrimitiveDateTime and OffsetDateTime, I really meant the string representations of those types, because everything internally should be OffsetDateTime
Ed Page
@epage
So just supporting parsing more string formats? Yes, we need to support more formats
David J. Weller-Fahy
@djwf
yeah, I think parse_date_time will check for timezone offset, then add the local offset if one is not present, and only then use the DateTimeImpl::parse method. That's probably the easiest way to do it.
David J. Weller-Fahy
@djwf
Ed - didn't know if you want me to merge the PR, or you (in general, I try not to merge PRs I generated)
Ed Page
@epage
Just hadn't gotten to it yet
Done
David J. Weller-Fahy
@djwf
Thanks - is there anything that I should look at next?
Ed Page
@epage
The things pressing on my mind the most for liquid are
• Adding the newest style of include and making sure all three are compliant
• Updating the conformance tests
• Experimenting with a nom based parser that provides a toolbox of parser that can be split out into its own crate with indepndent versioning, kind of like how regex has regex_syntax. To reduce exposing too much implementation details, the current parser API is fairly rigid
David J. Weller-Fahy
@djwf
Got it - I'll poke around a bit, thanks!
David J. Weller-Fahy
@djwf
so the goal of the nom parser would be to have a crate syntax that would contain the sum total of the syntax parsing, and could be used by other crates within our project, correct?
Ed Page
@epage
It can't provide a complete top-level syntax because the grammar is pluggable but it should allow for incremental parsing. This would then be used by blocks and tags to parse their their arguments and content. Its broken out so we can freely change i without breaking the rest of the API, like regex_syntax
I also find pest slow to compile and unergonomic to work with
David J. Weller-Fahy
@djwf
Makes sense - I like the combinator method better than an overarching parser. I'll start stubbing it out, and will probably bug you about overall design after I get a feel for it.
Jaafar
@jaafar:kde.org
[m]
Is there any way to do i18n/L10n in Cobalt or is that not supported right now?
Ed Page
@epage
There is not. cobalt-org/cobalt.rs#392 is the issue for it
Jaafar
@jaafar:kde.org
[m]

Yeah, I saw that. I just asked the question out of a false sense of hope as if there's another way to do it. :(

Moving to Zola is an option, but its huge distinction between sections/pages is kinda messing me up and forcing me to completely rethink everything from scratch. I'll see what I can do.

If this is the end for me and Cobalt, then it's been fun, and I thoroughly enjoyed the software. I salute and appreciate the developers and their amazing efforts. Sorry if I sound oddly dramatic here, but I really mean it. :)