In 1968 a British newspaper ran a competition for English translations of "Spleen - Je suis comme le roi..." The poet Nicholas Moore - motivated by a belief that translating poetry was impossible and the project futile - sent in 31 different entries, by post, under false names and with varying levels of absurdity. He didn't win.
You can find them at https://www.ubu.com/ubu/pdf/moore_spleen.pdf, or in his published Selected Poems, along with an essay (written afterwards) about translation. Worth looking out.
(I particularly admire the sarcastic one that begins "I'm like The Winner of The Competition / The one who wrote the strong, rewarding phrase...")
I'm just about old enough to remember (in the UK) foolscap paper, an imperial size also a bit longer than A4. You never see it any more (at least I don't) but foolscap sized box-files are still readily available. I guess a slightly bigger box than you need is not usually a problem.
Huh, this explains why some of my older teachers would call a4 pads as foolscap pads. I guess the paper size had been updated by the time I got to school, but their terminology wasn't.
This was my attempt at doing something a little bit like it, 27 years ago. It's mostly interesting as a historical artifact - certainly yours is a lot more sophisticated and much much prettier! This one just does greedy matching against CEDICT.
What is kind of interesting is that the script itself (a single Perl CGI script) has survived the passage of time better than the text documenting it.
Besides all the broken links, the text refers throughout to Big-5 encoding, and the form at https://all-day-breakfast.com/chinese/big5-simple.html has a warning that the popups only work in Netscape or MSIE 4. You can now ignore all of that because browsers are more encoding aware (it still uses Big-5 internally but you can paste in Unicode) and the popups work anywhere.
There's a link to the Perl code hidden in the third para of text ("The [Perl source] for this script is available...") Of course a big reason it still works is that it was written for Perl 5, which is still current!
My Chinese got somewhat better, then a lot worse, then a little bit better again - obviously mostly to do with whether I was actually using it, which on the whole I haven't been. But back then I was really working on it and I just wanted something to help - there were a few useful resources I knew of (CEDICT obviously, and Rick Harbaugh's zhongwen.com was mindblowing at the time) and this seemed like a way to glue them together that I actually knew how to do.
Writing learning tools is obviously not the same thing as learning though.
> I think that's probably what chordify.com does [...] I don't think they are using chordino
I think they were initially using the Chordino chroma features (NNLS-Chroma) but a different chord language model "front end". Their page at https://chordify.net/pages/technology-algorithm-explained/ seems to imply they've since switched to a deep learning model (not surprisingly)
Oh this is very nice, I hadn't seen it before. A few random thoughts:
- The Vamp Plugin Pack for Mac finally got an ARM/Intel universal build in its 2.0 release last year, so hopefully the caveat mentioned about the M1 Mac should no longer apply
- Most of the Vamp plugins in the Pack pre-date the pervasive use of deep learning in academia, and use classic AI or machine-learning methods with custom feature design and filtering/clustering/state models etc. (The associated papers can be an interesting read, because the methods are so explicitly tailored to the domain)
- Audacity as host only supports plugins that emit time labels as output - this obviously includes beats and chords, but there are other forms of analysis plugins can do if the host (e.g. Sonic Visualiser) supports them
- Besides the simple host in the Vamp SDK, there is another command-line Vamp host called Sonic Annotator (https://vamp-plugins.org/sonic-annotator/) which is even harder to use, equally poorly documented, and even more poorly maintained, but capable of some quite powerful batch analysis and supporting a wider range of audio file formats. Worth checking out if you're curious
(I'm the main author of the Vamp SDK and wrote bits of some of the plugins, so if you have other questions I may be able to help)
> No-one ever called a real program an "app" before that, did they?
Yes. Apple called them apps in the 80s, at least on the Mac - this is Apple II but it's plausible they were also referred to as apps there?
For my part I read the title as "Taking over a wall changed my direction as a programmer" which had me really confused for a while. I'd like to read that article, I think.
Apple (App-le?) certainly popularized abbreviating "applications programs" or "application software" (vs. system software, systems programs etc.) to "applications" in the 1980s, and "apps" with the advent of the App Store in 2008, but Apple was unsuccessful in trying to obtain and enforce an App Store trademark given prior uses of app, store, and app store (including, perhaps ironically given Steve Jobs' return and Apple's acquisition of NeXT, a store for NeXTSTEP apps.) "Killer App(lication)" dates to the 1980s, applying to software like VisiCalc for the Apple II.
The April 1984 issue of the British magazine "What Micro?" (70p from all good newsagents) contained a spoof review of a revolutionary new PC, the "Victori XZ64/4A".
A paragraph in praise of its display reads:
"Now lets move on to the display - and what a display it is. No less than 30 colours are available from Basic: white, off-white, cream, dark cream, light tan, light brown, bamboo, medium tan, medium brown, wood brown, sepia, burnt umber, oxtail, mustard (both French and English), khaki, off-brown, chocolate, dark tan, dark brown, dark burnt umber, burnt chocolate, drinking chocolate, ovaltine, light black, medium black, dark black, brown with a hint of green, brown with a hint of red, and brown with a hint of reddy-green. On some televisions these colours tend to look a little muddy, but with a little hunting around compatible sets can be found. For the purpose of this review I am using a VictoriVision Super Compatible available at most good electrical shops in Taiwan."
Qt does have a locale-aware equivalent (QLocale::toUpper/toLower) which calls out to ICU if available. Otherwise it falls back to the QString functions, so you have to be confident about how your build is configured. Whether it works or not has very little to do with the design of QString.
I don't see a problem with that. You can have it done locale-aware or not and "not" seems like a sane default. QString will uppercase 'ü' to 'Ü' just fine without locale-awareness whereas std::string doesn't handle non-ASCII according to the article. The cases where locale matters are probably very rare and the result will probably be reasonable anyway.
In some sense car manufacturers do do this - their designs are famous for being full of functionally empty retro cues that customers nonetheless go for.
You can find them at https://www.ubu.com/ubu/pdf/moore_spleen.pdf, or in his published Selected Poems, along with an essay (written afterwards) about translation. Worth looking out.
(I particularly admire the sarcastic one that begins "I'm like The Winner of The Competition / The one who wrote the strong, rewarding phrase...")