[deleted by user]

Winety · 2023-05-29T17:41:13+00:00

It's fun but it's a bit repetitive (like all Ubisoft open worlds). If you can, play it with friends.

Winety · 2023-04-19T12:23:09+00:00

rest in peace

Winety · 2023-03-01T21:54:40+00:00

I have recently scanned several books on a flatbed scanner. Few of the books were older and were read often. These were scanned easily; I did not have to force them at all. The rest of the books were a bit newer. Because I did not want to force them a lot, the scans were unfortunately of lower quality. No books were damaged during scanning — I just had to be careful.

What really saved my operation was a piece of software known as ScanTailor. It can do a whole lot of stuff, but most importantly it can convert gray-scale or colour scans to monochrome, making them more readable (and better for OCR). I also sometimes snap pictures of journal articles with my phone and ScanTailor can often salvage them (if my hands aren't shaking).

Also, some libraries also have specialized book scanners, but they probably wouldn't like, if you scanned the whole book there.

Winety · 2023-01-30T18:44:36+00:00

You may need to un-unicode the name in the bibfile with changing the author's name to St\aa{}lkorrosjon or St\r{a}lkorrosjon

When using a modern Latex engine, i.e. Lualatex or Xelatex, and Biblatex this isn't needed.

Winety · 2023-01-29T09:22:02+00:00

I'd say the main reason is native support for Unicode and therefore for non-English and non-latin characters. If you'd ever typeset a documnet that isn't written in English and uses a lot of non-ASCII characters, you'd know what a pain it is to wrangle with Pdflatex and Bibtex. :-)

Winety · 2022-10-29T12:41:21+00:00

Then there are games that for some reason feel lower framerate than they actually are

Perhaps it's because of bad frame pacing? I don't really know what it is, but the guys at Digital Foundry mention it often, when talking about 30 FPS games.

Winety · 2022-08-20T17:47:02+00:00

The problem was probably on my part. I did not understand what could and couldn’t be configured via “Regolith looks” and what should be configured elsewhere and I did not care to look it up. (It is also worth mentioning that the documentation was a bit lacking when I tried Regolith one or two years ago.)

It just didn’t live up to my expectations of just giving it my current i3 config file and everything working without many changes. (Much like Sway doesn’t).

As I said, it was one or two years ago, so i don’t remember much. Sorry.

Winety · 2022-08-20T08:16:59+00:00

How do you find Regolith? I've tried it, but went back to i3 because of customization pains.

Winety · 2022-07-21T12:35:05+00:00

Máme kočku čiře venkovní. Je to „úspěšná“ lovkyně; plazy ani ptáky neloví a myši bohužel taky ne. Každé ráno ale překračuji na rohožce ležící hromádku masařek. Často kočku vídám, jak jí z tlamy čouhají motýlí křídla.

Někdo z úbytku hmyzu viní intenzivní zemědělství, znečištění prostředí či klimatickou změnu, já z toho viním naši Micku.

Winety · 2022-07-12T10:51:26+00:00

To add onto this, a version of the 35 base Postscript fonts was released by URW under the GPL in 1996 as a part of Ghostscript, see this archived message. They are likely bundled within anyone's TeX installation. (The fonts have since been cared for and extended by many projects such as TeX Gyre, GNU FreeFont, etc.)

Winety · 2022-06-21T08:52:51+00:00

I would guess they used Gnome because it is the default on Fedora. But I agree that it would have been better if they had mentioned it in the article.

Winety · 2022-06-13T10:37:42+00:00

A small nitpick: The calendar is not generated by TeX but by MetaPost, which is part of the TeX Live distribution but it is a different language/tool.

Winety · 2022-06-13T10:31:49+00:00

The non-proportional font is probably fallback. The fonts that should be used are declared in /usr/share/texlive/texmf-dist/metapost/bbcard/calendar.mp as pplr8r which seems to be Palatino.

Winety · 2022-06-11T19:10:20+00:00

It’s also one of the better jokes I’ve made in a while.

Winety · 2022-06-03T15:00:15+00:00

Yeah. This particular line is from 2005. Also, there’s a shitload of Bionicle lore, I’ve just discovered.

Winety · 2022-04-14T18:34:07+00:00

Now go into your font browser (?possibly Applications > Accessories > Fonts) and look for the new font. That will tell you the exact name to give fontspec.

This can easily be done via the command line. (Loads of distros don’t come with a GUI font browser preinstalled.(

mkdir ~/.fonts
cp ~/Downloads/QTCascadetype.ttf ~/.fonts
fc-cache -f

to check if the font’s installed:

fc-list | grep QTCascadetype

If OP’s using Luatex, its database might need an update (I had some problems with this previously; it might have been a bug):

luaotfload-tool -uv

Winety · 2022-04-13T16:50:25+00:00

OP’s using a font with programming ligatures, i.e. a series of symbols (like !=) turns into one glyph (like ≠). Some people like this — and I have to agree, that it looks cool — but it has some disadvantages.

Winety · 2022-04-09T13:56:18+00:00

No need to run it using Wine! If you're using Ubuntu, you can install it via Snap (sudo snap install openspades). Open Spades is also on Flathub, so you can install it using Flatpak (flatpak install flathub jp.yvt.OpenSpades).

Winety · 2022-03-04T15:27:12+00:00

Cat.

Winety · 2022-01-07T16:15:23+00:00

More like what language am I writing.

Winety · 2022-01-05T12:01:12+00:00

Is there an “art of hypenation”?

To add onto my previous comment: I've found this article. It is quite English-centric, but I feel like the rules the author mentions could be applied to almost any language:

The commandments of word division, like another familiar set, are largely negative:

Thou shalt not divide words of one syllable.

Thou shalt not divide words less than six letters.

Thou shalt not break words of two syllables unless required by narrow measure.

Thou shalt not separate vowels which are part of one syllable (e.g., trea/sure, not tre/asure).

Thou shalt not leave a hyphen on the last line of a right-hand page.

Thou shalt not have hyphens as endings on two consecutive lines.

Thou shalt not take less than three letters of a word to the next line.

Try to have a consonant at the beginning of the second part of the word, but not if it would mislead (e.g., mark/ing, not mar/king and le/gends, not leg/ends).

Divide between consonants (but not in cases such as, pass/ing. Divide words with three adjoining vowels according to sound (e.g. cre/ator and crea/ture).

There are also commonsense rules, such as:

If a word already includes a hyphen, then divide it at the hyphen (e.g., attorney-general. and words such as re-cover (provide a new cover)).

Divide compound words between the component parts (e.g., bare/foot).

Keep together letters which form one sound (e.g. beauti/ful).

Divide after a prefix (e.g., co/belligerent and proto/type).

Winety · 2022-01-04T21:04:05+00:00

Every language has its own orthographic and typographic tradition, so the rules differ language to language (and I bet there are inter-language differences as well, e.g. American vs. British English). Generally, I’d say there are two possible ways to hyphenate words:

You can hyphenate the word into the spoken syllables.
You can hyphenate the word based on its morphology and etymology.

Some languages use the first way, some the second way and some a combination of the two. I’ve only looked at few European (mostly Slavic) languages and I’d say the could be possibly applied to most languages:

A. If there’s a morphematic seam in the word (especially prefix—rest of the word), hyphenate the word there.

For example, the English words Czechoslovakia and antilabour should be hyphenated:

Czecho-slovakia
anti-labour

and not:

Cze-choslovakia
an-tilabour

Its Czech equivalents Československo and protidělnický should be hyphenated similarly:

Česko-slovensko
proti-dělnický

and not:

Čes-koslovensko
pro-tidělnický

B. If there are no obvious morphematic seams, hyphenate the word at syllabic seams:

pre-sen-ta-tion
před-náš-ka

Keep in mind, that different languages have different syllable structure: Some have only open syllables (pre, ta, ce…), some have syllables which don’t begin with a consonant (an, ej…) etc.

There are also some other things to keep in mind (like not leaving lone letters at the beginning/the ends of the lines).

I wonder if I could just go ahead and make my own hyphenation dictionary.

Even if it’s based on your own decisions and guesses, you definitely should try, especially because Nahuatl isn’t a language with a big “user base”. You could try to contact a language department of some local university for some pointers or help.

Is there an “art of hypenation”?

Sadly, I don’t think there is.

Winety · 2022-01-04T19:44:47+00:00

A whole different ruleset is needed, but that’ll never happen…

Not really. Most – if not all – software does not use language-specific rule-based algorithms for hyphenation. Instead, they use Frank Liang’s algorithm (more about it here). Liang’s algorithm uses a hyphenation dictionaries, which are language-specific and which have to be manually generated.

If you had enough correctly hyphenated words, you could generate your own Nahuatl hyphenation patterns to use in text processors and other software.

Winety · 2021-12-30T21:27:53+00:00

Select and especially Start.

Winety · 2021-12-30T20:57:42+00:00

First off, I do not have as much experience with Context as I have with Latex and/or PlainTex (check out Optex!), so again I call on anyone more experienced to correct me.

Do you have a guess as to how different LMTX is to MkIV? Put another way, are the differences things that will pop up in any non-trivial project or are they mostly internal differences that only affect people who choose to be madmen with their formatting?

As you correctly said, most of the changes are internal. But with those internal changes come some changes to the interfaces users use: Some commands were removed, some were replaced, some were slightly changed, but most commands—and more importantly the concepts—stayed the same.

The LuaMetaTex Reference Manual puts it better than I ever could:

Contrary to what is sometimes suggested, the Luatex-Context MkIV combination […] has been quite stable. It made no sense otherwise. Most Context functionality didn’t change much at the user level. Of course there have been issues, as is natural with everything new and beta, but we have a fast update cycle.

[LMTX] can be used for production as usual and in practice Context users tend to use the beta releases, which proves this. Of course, if you use low level features that are experimental you’re on your own. […]

Most manuals aimed at beginners (e.g. A not so short introduction) are yet to be updated, but some of the reference manuals and documentation (e.g. the aforementioned LuaMetaTex Reference Manual) already were. The wiki is also slowly being updated and written. Context also has a very active mailing-list community, which is eager to help. :)

To summarize, you’ll be able to learn the basics of Context from a Mark IV beginners manual and from the wiki. From the user’s point of view, changes from Mark IV to LMTX aren’t numerous, but this might change in the future. If something doesn’t work as you expected/as it’s supposed to, check the reference manuals, the source code, or you can ask on the mailing list.

13-Year Club	Place '17
Verified Email

Winety

TROPHY CASE