sile-typesetter / sile-typesetter.github.io Goto Github PK

We're successfully building examples (when necessary) using devel builds (Git HEAD at the time of site update) to showcase upcoming features, but we need to flag the examples in the showcase so people don't mistakenly thing they can use the code with only a stable tag release.

e.g. Dropcaps from #26 are currently devel only.

Then I'm trying to fetch documentation from official Sile site (http://www.sile-typesetter.org/what-is/index.html) via link
https://github.com/simoncozens/sile/blob/master/documentation/sile.pdf?raw=true nothing happens :-(

Hello,

A link to the pdf manual is broken from site subsections:

• http://www.sile-typesetter.org/examples/index.html
• http://www.sile-typesetter.org/what-is/index.html

With the best regards

This entire repository is predicated on the assumption @simoncozens is in agreement with @rjmunro's comment here. **If not we can just delete this whole repo and go our merry way. **

I do think there is an advantage to having the site repository split. It will make cloning the main project that might lighter (as the binary blobs in this repo be excluded), separates the issue tracker, and will make tooling for automated released easier. Trying to manage CI build triggers in branches is less complicated that just triggering things on another repo.

To that end I extracted the gh-pages branch from the main sile repo and pushed it as the master branch of this repo.

Remaining tasks will need to be done by Simon since they involve the domain...

• Verify the domain under the org account here.
• Disable the GH Pages feature from the sile repo here by setting the "source" to none and removing the custom domain entry
• Enable the GH Pages feature for this repo.
• Add the custom domain to this repository here.
• Update deprecated IP addresses of GH Pages service from DNS records.
• Fix whatever you have to do so that HTTPS works and is Enforced.
• Delete the gh-pages branch from the old repo here so that clones and forks stop picking it up.
• Transfer all site related issues, see #9.

So http://www.sile-typesetter.org/ works but http://sile-typesetter.org/ does not. There should be the redirect.

(IMHO, better to make address without www the default one)

This is probably as much my personal taste as anything else, but I very strongly dislike Jekyll. And always have really. I don't like Ruby and I find the allowed repository layout and output very restrictive. The fact that GitHub heavily restricts which plugins can be used just adds frustration to my dislike.

These days publishing on GitHub pages can be done by almost any static site generator using Actions. At some point I'd like to covert the sources to a different SSG. My current favorite is Zola, but Hugo would also be in the running and there are half a dozen others that I consider good (and half a hundred I don't).

I am in the process of compiling a few sample pages for typesetting Anglo-Saxon scripture.
I would like to donate some of these to the examples if appreciated.

Draft here:

https://github.com/StefanSchroeder/sile-stuff/blob/master/anglo.pdf

I was just on one of my periodic visits to the SILE website, and was looking again at the manual. It struck me as odd that the ToC dot leaders aren't right-justified, and are even somewhat ragged when you would expect some consistency:

Is that by design? It strikes me as aesthetically a bit odd, and especially curious for an potential "shop-window" for a typesetting program!

Anyway, thought I'd mention it, FWIW. (And hi, @alerque!)

http://www.sile-typesetter.org/examples/ has no images or CSS, and /what-is/ has no CSS.

The Manual (PDF) link in the sidebar raises a 404 for the 0.14.2 PDF manual.

The basic typography design of the current site needs a full overhaul. Notably header and list items have really weird spacing, but other 'features' add to the chaos and make a fairly unpleasant reading experience (which of course is awkward given what sile does).

c.f. #2

I suggest refactoring the website examples a bit:

• I know I just got done moving many of the examples from the sile repo to this website repo, but I would like to move some of them back. In particular now that the package system is much closer to expecting packages to be idempotent and each package has a dedicated subdirectory instead of living in a zoo, I think it might make sense for there to be one example entry per package stored next to the package sources. This would not be managed by whoever was maintaining the package & documentation. We could make rules like they must work in the plain class, etc. That would aid our testing a bit because we could have a whole class of tests that just made sure packages function and their showcase documents build (different from point-perfect regression testing). Additionally we could build the PDFs that showcase each package and embed a shrunken version of them as thumbnails in The SILE Book at the start of each package's documentation.

• The could go for classes and ever languages: one showcase document that at least runs each function once in isolation (as opposed to the current approach to manual that loads all packages in the main document class) could be useful, but for SILE testing and a more complete source of examples for the website.

• With those done, the website repository could focus on mixed use showcases, more "show and tell" sort of examples that use an assortment of tools. They could be tagged with what packages/classes/languages they showcase and be show along with the upstream showcase for specific packages.

Two links to the example PDFs on the Example page are broken. Links on the other pages ( Global Scripts, Packages) seems to be working.

This issue is maybe related to the Build website as static sources without hotlinking SILE repository.

I've downloaded the manual from the website and the repo in Safari and Chrome and none of the PDF's can be opened on my mac w/ either Preview or Acrobat.

From the mostly obsolete SILE issue:

Gah! So close and yet....

It works for me locally:

$ nix run github:sile-typesetter/sile -- --version
SILE v0.12.5-72b25f3-flake (Lua 5.3)

But CI bombs out with a cryptic:

error: attribute 'defaultApp.x86_64-linux' should have type 'derivation'

Same version of nix (2.9.1) in both places, same channels (I think) and same config options (seemingly irrelevant experimental flags leftover from previous versions, but tried with and without).

We use both the last stable release and the HEAD to generate examples on the website. The stable version comes out of Nix packages, the HEAD version from the flake.

For some reason while I can run it locally the Flake doesn't work from CI.

Before trying to use it we double check that we can run it:

https://github.com/sile-typesetter/sile-typesetter.github.io/blob/master/.github/workflows/deploy.yml#L40

That's the line that's failing.

Note I've been testing this on my fork.

Any ideas @doronbehar?

The spacing after code blocks needs some help.

Bringing native math support, the next SILE release is likely to get a little more publicity than usual. As such it might be nice to prepare for it just a little more than usual.

1. An introductory paragraph for release announcement on the blog that tells a little bit about the approach for folks that have been sticking to TeX just for the math.
2. An new example or two to put up as an image showcasing something it can do.

@OlivierNicole Are either of these (or anything else that you suggest should go into the release) be something you can help with?

Hotlinking stuff in the SILE repo from the website is ... fragile at best. I think we should restructure it so that examples are updated a different way. I can think of several ways, but relying on PNG images in a source repo is not one of them. Keeping example sources on the website and using CI to build them using SILE as a runner to generate PDF / PNG / whatever output might be one of them.

For history & context having site related issues here seems like a good thing. I migrated all the issues that were directly related to the site. Links to migrated issues auto-redirect to their new numbers on this repo.

PR's cannot be migrated, but in the event the history is relevant:

• sile-typesetter/sile#291
• sile-typesetter/sile#289
• sile-typesetter/sile#375

Also mentions in these issues, but as long as the related source is in the sile repo it seemed like leaving the related issue was best.

• sile-typesetter/sile#12
• sile-typesetter/sile#343

Hi, I'm trying to use SILE as a library as told in its manual but getting the same error every time:

lua: byhand.lua:29: attempt to call a nil value (field 'typesetter')
stack traceback:
        byhand.lua:29: in main chunk
        [C]: in ?

These two links from https://sile-typesetter.org/examples/:

• https://raw.githubusercontent.com/sile-typesetter/sile/master/examples/simple.pdf
• https://raw.githubusercontent.com/sile-typesetter/sile/master/examples/book.pdf

I suppose they were dropped in e74f72326b917b88a301f844670cc47f7f7cb3ba, a year ago.

This is my first time looking at SILE, and I am excited, because of this line in the manual:

it contains a slavish port of the TeX line-breaking algorithm which has been tested to produce exactly the same output as TeX given equivalent input

(and more importantly I even see the box-glue-penalty model with similar parameters like penalty=-10000).

Knuth always intended others to take his ideas and programs and write new programs (that's why he published all his TeX work as papers, and even the entire source code as a book in readable form), and it's nice to see that someone's actually doing it seriously finally.

But what are some purposes that SILE has been used for (other than by its author), or examples of what SILE could be used for? I wasn't able to satisfy my curiosity about this from the homepage. Looking around in the Github repo, I was able to find a few examples at https://github.com/simoncozens/sile/tree/master/examples . For example, this one is quite interesting to me: https://github.com/simoncozens/sile/blob/master/examples/parallel.pdf

Most people grasp things best by examples, so my humble suggestion would be to put as many examples as possible (images and SILE source code) on the homepage. It might attract more users…

The left navbar of the website has two entries labeled Home.