shoeffner · HackerTrans

I use pass to manage such things separately. This allows to script around hard-coded secrets:

     export MY_TOKEN="$(pass token | head -n 1)"

shoeffner

3 年前議論

Pandoc even poses codeblock execution as an exercise in their custom-filter documentation: https://pandoc.org/filters.html The python package panflute is also really nice if you don't want to play around with haskell or the AST JSON directly.

shoeffner

3 年前議論

Fraunhofer Institute for Digital Medicine MEVIS | Public sector collective wage agreement | Full-Time | Bremen/Lübeck/Berlin, Germany | DevOps Engineer

At Fraunhofer MEVIS we pursue a patient-centered and clinical workflow-oriented approach to solving clinically relevant challenges in image- and data-based diagnosis and therapy (e.g., MRI analysis and surgery planning). To deliver excellent results, our research and development teams increasingly rely on our on-premises cluster and cloud infrastructure to compile, test, and deploy our software products, or train state of the art deep learning models.

As a DevOps Engineer, you will join a motivated team and improve the on-premise infrastructure. Our daily work involves the HashiCorp stack (Nomad, Vault, Terraform), Puppet, Ansible, OpenStack, and more. Additionally, we support our research personnel with CI/CD setups employing Jenkins and GitLab.

For more information, visit our job board or contact me directly:

https://jobs.fraunhofer.de/job/DevOps-Engineer-Digital-Medic... [email protected]

shoeffner

5 年前議論

It's below the related and recommended products.

shoeffner

5 年前議論

What do you mean? I tried placing Ö and {\"O} in the author's name of the example and tidied it:

    Click Tidy to clean up the entries below      
    @Book{sweig42,
      Author =  { Stef{\"O}{n} SwÖig },
      title =  { The impossible book },
      publisher =  { Dead Poet Society},
      year =  1942,
      month =        mar
    }

This is the output:

    Click Tidy to clean up the entries below
    @book{sweig42,
     title        = {The impossible book},
     author       = {Stef{\"O}{n} SwÖig},
     year         = 1942,
     month        = mar,
     publisher    = {Dead Poet Society}
    }

And \"O should be Ö, so I guess I do not really understand what is "incorrect" in your use case.

I know that the Zoteroplugin BetterBibTeX converts Ö to {\"O} when exporting as BibTeX, but keeps it as Ö when exporting as BibLaTeX – maybe Kbibtex has similar options?

edit: It actually "fixes" Ö to {\"O} if you tick "Escape special characters" or supply the command line argument `--escape`, which should be the default according to GitHub.

shoeffner

5 年前議論

In the example "Straße", the ß is, in fact, derived from an ancient ligature for sz. Old German fonts often had s as ſ, and z as ʒ. This ſʒ eventually became ß.

We (completely?) lost ſ and ʒ over the years, but ß was here to stay. Its usage changed heavily over time (replacing ss instead of sz), I think for the last time in the 90s (https://en.wikipedia.org/wiki/German_orthography_reform_of_1...), where we changed when to use ß and when ss.

So while we do replace ß with ss if we uppercase or have no ß available on the keyboard, no one would ever replace ß by sz (or even ſʒ) today, unless for artistic or traditional reasons.

Many people uppercase ß with lowercase ß or, for various reasons, an uppercase B. I have yet to see a real world example of an uppercase ẞ, it does not seem to exist outside of the internet. For example, "Straße" could be seen capitalized in the wild as STRAßE, STRASSE, STRABE, with Unicode it could also be STRAẞE. It would not be capitalized with sz (STRASZE) or even ſʒ (STRAſƷE – there is no uppercase ſ) – at least not in Germany. In Austria, sz seeems to be an option.

So, for most ligatures I would agree with you, but specifically ß is one of those ligatures I would call an outlier, at least in Germany.

P.S.: Maybe the ampersand (&), which is derived from ligatures of the latin "et", has sometimes similar problems, alhough on a different level, since it replaces a whole word. However, I have seen it being used as part of "etc.", as in "&c." (https://en.wiktionary.org/wiki/%26c.), so your point might also hold.

P.P.S.: I wonder why the uppercasing in the original post did not use ẞ, but I guess it is because of the rules in https://www.unicode.org/Public/UCD/latest/ucd/SpecialCasing.... (link taken from the feed). The wikipedia entry says we adopted the capital ẞ in 2017 (but it is part of unicode since 2008). It also states that the replacement SZ should be used if the meaning would otherwise get lost (e.g. "in Maßen" vs. "in Massen" would both be "IN MASSEN" but mean either "in moderate amounts" or "in masses", forcing the first to be capitalized as MASZEN). I doubt any programming language or library handles this. I would not have even handled it myself in a manual setting, as it is such an extreme edge case. And I when I read it, I would stumble over it.

shoeffner

5 年前議論

You need to press enter/return to advance.

コメント