Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)N
Posts
4
Comments
940
Joined
2 yr. ago

  • Oh, for "how do they show emphasis" - nowadays I'd say it's mostly like this which in many apps will actually make text bold or italic. But we don't have a way to "shout" like ALL CAPS WRITING IN ENGLISH. It's just not a thing. Often, I wish there was a way.

  • Hebrew does not have capital letters. But it does have "cursive": https://en.wikipedia.org/wiki/Cursive_Hebrew . In Hebrew it's usually just called "handwriting" (כתב, כתב יד) as opposed to "print" (דפוס). The letters don't flow into each other like they do in Latin cursive. They're just faster to write.

    In Unicode, each letter has just a single code point: e.g. ק is Hebrew Letter Qof (U+05E7). If you want cursive, you use a cursive font, but it's still the same character.

    Some letters have a different final form: if they are the last letter in a word, they look different. These are encoded as different characters, for example: the final form of צ Hebrew Letter Tsadi (U+05E6) is ץ Hebrew Letter Final Tsadi (U+05E5). There is a separate key for it on the keyboard.

    There's also niqqud, which takes the job of vowels, but that's a whole other can of worms and isn't used in everyday writing. It's only very rarely used to clarify an otherwise ambiguous word.

  • (Comedy answer)

    Seems like you have a tendency to get terrible jobs. Try the George Costanza method: whatever your instincts tell you to do, do the opposite! You'll be working at the New York Yankees in no time.

  • I followed a number of guides to try to get it to work. Including doing that. No dice.

    I still think it's probably user error on my part, but I'm still shocked there was no command to effectively "force run an unattended upgrade now" to test that it works correctly.

  • The OP did it in the wrong order. First do update to refresh, then do upgrade to install.

  • There are even better ways built into the shell, but I can never remember any of them. I also never thought of history|grep, I think I might actually remember that one. Thanks!

  • It's through Update Manager (mintupdate) for me, but I definitely feel like the happy guy looking out at the nice view.

  • I never got unattended-upgrades to work for me on the machine I tried it on. Best I could tell, it just didn't do anything. It was frustrating.

    But many years back I set up my raspberry pi with a cron job that was effectively (if not literally) apt update && apt full-upgrade && reboot and that seemed to be working just fine.

  • The net is quite captivating.

  • I can name a couple of apps that try to recognize songs from the microphone:

    SoundHound - my favorite. For most songs I've used it for, it recognizes exactly where in the song it was and shows you the lyrics, highlighting the active line and updating live, so you can follow along.

    Shazam - most popular and well-known (at least we're I'm from)

    Google - you can use the microphone to search. Has the best chance of recognizing songs through humming or singing in my experience.

  • אני לא מכיר קהילות בעברית... והאמת שאני באופן אישי גם לא ממש מחפש אותם

  • I speak Hebrew, what do you want to know?

  • What is the joke, or message, or point of this comic? I see no connection between the 3 panels other than the same character appears in them.

  • But why?

  • Second one is reversed.

    The world: "Will you take this Palestinian state?"

    Palestine: "No"

    As for the others, well, it's always more complex than that but sure, for the point you're trying to make I guess it's close enough.

    Edit: actually I take it back about the rest. I simply don't know enough. So it's anywhere between close enough or grossly inaccurate.

  • Bidirectional text only really occurs when mixing languages

    And also any time numbers are used in RTL text, which is pretty common. Besides, you might be surprised how often English words or acronyms are used in everyday texts. If there's a news story covering the American FBI, there's no way to avoid writing it as "FBI", in Latin letters.

    There are a lot of top-to-bottom languages in Asia. Some chinese languages for example are traditionally written top to bottom.

    But is that how it's rendered by default when typed into a computer, for example into Notepad? Or into a chatting app like WhatsApp, Telegram, Discord, etc.? To my knowledge, they are rendered horizontally unless the software is specifically configured to render them TTB.

    But I'm guessing even though Unicode's stated goal is to encode all writing, TTB is probably where they drew the line.

    I believe there actually are a few TTB properties in the Unicode database.

    except that one language that also uses RTL digits. I don't remember its name or where it's used, but it exists.

  • I'm most cases, a consecutive run of RTL or neutral characters would be rendered RTL, while the rest would be rendered LTR. However, if it's within a RTL paragraph, this would be reversed.

    For example, the following two paragraphs have the same path, but the surrounding text is translated:

    Open C:\Users\אדם\Documents\דברים\מסמך.pdf and click "Sign".

    פתח את C:\Users\אדם\Documents\דברים\מסמך.pdf ולחץ על "חתימה".

    Depending on your client, these should be rendered differently. If they don't, click here to see it: https://jsfiddle.net/jex3yfrw/

    Edit: looks like Voyager needs a bug report! The web Lemmy seems to render it RTL (correctly) but still left-aligned which is not ideal.

  • I'm not sure, as I've never used them. But I imagine this is a lot more straightforward.

    The problem with bidirectional text is that it's bi-directional. Parts of it are RTL and parts are LTR. The main problem is how to order the characters visually, assuming that they are stored in memory in the order in which they are intended to be read.

    For text that goes in only one direction this is trivial. LTR: characters are arranged from left to right. RTL: characters are arranged from right to left. Easy peasy!

    The problem, as I've said, is when you have a sentence or paragraph with both LTR and RTL text inside it. Then the algorithm is needed.

    To my knowledge, there is no bottom-to-top language, and certainly not one that would be mixed in within top-to-bottom text or vice versa. So an algorithm isn't necessary: if TTB (top-to-bottom) is used, characters simply need to be arranged top to bottom.

    To add on to this, I believe TTB text is only used explicitly. By default, all text is rendered horizontally (usually LTR) unless you explicitly set the software to render it top-to-bottom. So if you just have plain text in Japanese or whatever language with no additional markup, it will be rendered horizontally and subject to the UBA.