amake

It's important to distinguish that from the Pixar thing.

First, the Pixar thing was green pepper, not green beans: https://www.businessinsider.com/why-inside-out-has-different...

Second, the Pixar one is not "mere" translation; it is full localization because they changed the visual to match the "textual" change.

The Pokemon one is where the change was limited to the "text". The translator's heart might have been in the right place (it would depend on how integral to the story it is that the item is onigiri) but didn't have the authority to make the full breadth of changes needed for such adaptation to be successful.

Yes.

If it's worth doing, then it's worth doing correctly.

If not, then don't.

Why would I read a book that a person couldn't be bothered to write?

flouts

I am arguing this point, because it’s a huge flaw in the premise of the tool in question.

Yes, but it raises the question of what exactly the "character" count is supposed to mean.

Does anyone need a "UTF-16 code unit count"? Somehow I don't think so. So it should really be counting graphemes, in my opinion.

> Some emojis require two UTF-16 code units so yep, standard

But not acceptable in a "character counter", in my opinion. What exactly is the use case for this counter, since it won't align with anyone's real-world intuition for the meaning of "character"?

> I mean, if this uses the same calculation as Twitter, Instagram and other sites that limit characters

Almost certainly those sites use much more sophisticated counting schemes.

> Honestly, I don't know, I did not expect for this to go so deep

You're not the creator of the tool in question, so it's OK for you not to know about this stuff, but I would really expect more from someone who is setting out to create a "character counter" tool.

It's not counting "characters"; it's counting UTF-16 code units, so for instance a country flag is 4 "characters" because it's two regional indicator symbols, each composed of two surrogates.

It should really be using `Intl.Segmenter` instead of `string.length`: https://stackoverflow.com/questions/10287887/get-grapheme-ch...

As long as it's the only one supporting Manifest v2, I think it really is the best option.

> PNRG

You sure about that?

This is very similar to Japanese "flick" input:

https://www.youtube.com/watch?v=BhD6r8NKlmY

Sounds like a shitty system.

Socialism is good, actually.

> This aesthetic screenshot

What does "aesthetic" mean to you?

Perhaps you are not a translator. Translating is a skill that is more than simply being bilingual.

It was the killer app that got me hooked on Emacs (which I now use as my IDE and daily driver for almost everything except web browsing).

Every time I see tools like this I think "ah, the normies are reimplementing Magit".

iOS has provided a glyph for ⏻ U+23FB POWER SYMBOL since iOS 14:

https://tofu.quest/?q=%E2%8F%BB

(Full disclosure: I maintain a project that catalogs which Unicode codepoints are covered by the default fonts on iOS and Android ( https://github.com/amake/CodePointCoverage/ ); this feeds tofu.quest which is also my project.)

There seem to be some discrepancies between his table and the fonts contained in the repository. For instance, as of this comment the table says Noto Sans Miao Regular is missing from AOSP, but the repository apparently has had this since April 2023 (the author says he looked at the AOSP source code in September 2024):

https://cs.android.com/android/platform/superproject/main/+/...

Since he didn't link to a specific commit representing the version of AOSP he looked at, it's possible that this font really was added afterwards; I'm not going to go full archaeologist on this one. But at the very least it seems like the table needs another look.

"Unicode" seems to have (colloquially) taken on the meaning of "complete or extensive language support".

And if you want to work with fonts locally I recommend https://github.com/fonttools/fonttools

In particular the `ttx` tool is great for digging into the innards of font files.

> It’s really hard to know what to think about Elon Musk these days

Doesn't seem that hard, tbh

> The exaggerated examples of these counter-motions are called “woke”.

This is your definition. I doubt you will find any agreement on what "woke" means, because right-wingers use it to refer to anything and everything that they dislike.

Unrelated to the article content: I thought the headline typeface was lovely. It turns out it's Eskell Display: https://lettersfromsweden.se/font/eksell-display/

We specify an output schema (TypeScript syntax) in our system prompt, and OpenAI gets it right most of the time. With some regularity it will give invalid (per the schema) output like

- Return a single object instead of an array of objects

- Return an array of a single object instead of just the object

On the other hand I personally haven't seen it give malformed JSON; the JSON is well-formed but not compliant with the schema we specified.

This is trivially prevented by wrapping the body in a function that is executed only on the last line of the script. I don't think I've seen a "curl | sh" script in the wild that wasn't written that way.

"TUI" is "text(ual) user interface", not "terminal user interface". If the UI is (primarily?) made of text (which it is in Emacs' GUI mode) then it doesn't need to be in the terminal.

Seems like you might as well use Private Use Area characters[0] and keep things valid UTF-8.

(Yes, you will have problems with paths that contain PUA characters. But people have pointed out that paths aren't necessarily valid UTF-8, so you can't inline-encode your way out of this anyway. PUA characters are likely vanishingly less common than spaces, so you still mostly solve the problem.)

[0] https://en.wikipedia.org/wiki/Private_Use_Areas