Shared lexicon schemas for long-form publishing on AT Protocol. Uses typescript to json via prototypey.

Fork 3

Publication/document locale and localization in general #16

Open

niklaskorz.eu 3mo ago

Open opened by

niklaskorz.eu 3mo ago

While digging into standard.site and applications based on it, I came to realize that there does not seem to be any locale property declaring the language a document or publication is written in. This makes it harder to discover content in non-English languages I (want to) speak.

Furthermore, a way for documents similar to HTML link's rel=alternate to reference translations of the same document in other locales would be very handy for multilingual blogs like mine (I blog in English on korz.dev and in German on niklaskorz.de, all articles have a translated 1:1 mapping to the other). In that sense, I could imagine it would be handy to have both alternate relations between publications as well as between documents across publications, so that the English and German variants of my blog could be separate publications while the documents may still refer to each other as translated variants cross-publication.

brookie.blog 3mo ago

Coming soon! https://tangled.org/standard.site/standard.site/commit/9fbd51deb19c93ebea8193862b81e72df09e00f3

Still considering what would be the best way to handle multiple translations.

writizzy.com 2mo ago

Hi, I'm maintaining writizzy.com (a blogging platform using the standard.site)

I’d like to respond because I’ve actually been working on the topic of multilingual content. I did indeed use the hreflang alternate attribute. Multilingual content is managed through two publications. And each document within a publication uses the language of that publication.

Then I create a link between a document in one publication and a document in another publication, which allows me to insert the meta tags for multilingual content.

There’s a second option that’s sometimes used but that I haven’t implemented: having both languages in the same publication. But that wouldn’t change the logic much—one document would specify the language and then declare a link to the other document, which is the translation.

It seems quite natural to me to translate this into the lexicon in the same way, by copying the existing logic we use with hreflang attributes.