Live data from Hacker News

Creating a QR Code step by step

nayuki.io

21–30 of 49 posts

Re: Creating a QR Code step by step

#21
post #11

This resource is awesome. I wanted to have the smallest readable QR code for my printables pages footer [1], and I discovered there that it's possible to encode URLs in "Alphanumeric mode", version 1, using only uppercase characters, e.g., HTTPS://FOO.CC/ABCDEFGHIJ, so I got a three letter domain name and built the simplest URL shortener hosted on a CF worker. [1]: https://pdf.ahaprintables.com/pdf/preview/aha/zebra-…

Would you please share more information about it? Thanks.

Re: Creating a QR Code step by step

#25
post #4

A good practice is to tag the title with the year of the article (in this case, 2018), when it is not from the current year.

I agree, the original link to the post, doesnt have a date as far as i can tell, and I can't edit it anymore.

Re: Creating a QR Code step by step

#26
post #17

Unfortunately it seems that every online explanation of QR codes always leaves out the Reed-Solomon error code calculation. The author here describes it as “long, tedious, and not very interesting”, but since everyone seems to think that, it is now very hard to find.

I took a code theory course in grad school. It was the most rigorous course I took, and for all of the 5 students it was difficult, but I'm also really glad I took it.

Reed Solomon was about two thirds of the way through the semester, and the gist is that it's based on polynomials - with enough points you can define exactly where the polynomial is - so include some extra points and that way if some get lost along the way you can recreate them.

The rest of it is how to apply that for binary data (finite fields). Which is mathematically beautiful, but where they get somewhat complex.

Re: Creating a QR Code step by step

#28
post #14
post #2

The feedback he receives is quite fun: https://www.nayuki.io/page/poor-feedback-from-readers

The commentary mocking people for their poor English, followed by disparaging remarks about an entire country as if the email senders represent a typical sample from that nation, says more about the blog owner than about the email senders themselves. The blog owner exudes elitist vibes in the commentary. A quick skim of the blog reveals a request for Bitcoin donations, suggesting $3 as the amount, without considering…

Dude really doesn’t like Indians huh.

I can see why these racists come to the conclusion that all Indians speak a certain way. If they see something written with a few quirks common to Indian English they confirm their bias that all Indians speak and write that way. If they see text without that tell, their bias is still confirmed because they conclude this person must have grown up elsewhere.

For the racists at the back - language diverges over time. That’s perfectly normal. As the reader/listener it’s easier for us to make the effort to understand than it is for someone to change how they speak. If you’re ok with making an effort to understand unusual words and phrases used by Australian, Scottish, Irish, Kiwi people but you won’t do the same for Indian people, reflect on why you do that.

People from NZ change most “e” sounds to “i”, so they’d eat pincakes for breakfast for example. I find that quirk endearing. Or Australians using words like ute, jaffle etc. But somehow only white English speakers are given the benefit of the doubt when they do this? Why can’t Indians get the same thing when they’re speaking their second language?

Re: Creating a QR Code step by step

#29
post #25
post #4

A good practice is to tag the title with the year of the article (in this case, 2018), when it is not from the current year.

I agree, the original link to the post, doesnt have a date as far as i can tell, and I can't edit it anymore.

Although the date is included in the article, it is located at the very bottom of the page, which is unlikely to be easily found. It reads: "Last updated: 2018-11-05"

Re: Creating a QR Code step by step

#30
post #17

Unfortunately it seems that every online explanation of QR codes always leaves out the Reed-Solomon error code calculation. The author here describes it as “long, tedious, and not very interesting”, but since everyone seems to think that, it is now very hard to find.

These two tutorials explain the error code calculations:

https://www.thonky.com/qr-code-tutorial/error-correction-cod...

https://dev.to/maxart2501/let-s-develop-a-qr-code-generator-...

Post reply on HN