ThaiNotes

Rong Kluea Market (literally "salt building market") Room 7 Thanon Wathana (this is a guess sinced ถว appears to be an abbreviation) Not sure what ค9 means. Perhaps a mistake and they meant Km. 9

It is oversimplifying. That's why the site has a reading course at https://thai-notes.com/reading/index.html The subject of unstressed "a" is covered in lessons 27 and 28. That covers the tone of the first syllable. Had you spotted that the tone of the second syllable is not what you'd expect? วัส = low class consonant + short vowel + dead final. According to the chart, that should be high tone. Indeed, วัด, which follows the same pattern is high tone, /wát/. However, in สวัสดี วัส is low tone. That's also covered in lesson 27. I would suggest: (1) You use a dictionary that gets the tones right. I've previously linked to Haas. The other one I would suggest is at https://thai-notes.com/dictionaries/predictionarysearch.html but it does not include glottal stops in the transcription. Wait until you can read Thai script fluently and accurately, so can ignore then transcription, before using the likes of thai-language. (2) Work your way through the reading course (link above). There are so many complexities and irregularities with written Thai, it would take an age to learn about all of them working piecemeal. Finally, let me pick you up on one tiny thing: ส is not a "high tone consonant" , it's a high class consonant. There is no direct relationship between a consonant's class and the tone is produces.

It is not low tone. It's mid tone in normal speech because the syllable is unstressed. If you have a look at the Haas Thai Learners' Dictionary (available online at https://thai-notes.com/dictionaries/haas.html) you'll see it's pronounced /saˈwàtˈdii/. Note it also doesn't have a glottal stop. (For comparison, สระ with a stressed "a" is transcribed as /ˈsàʔ/ - same source.) Thai people have a false view of how their language is pronounced, probably because they can't actually spell out a mid tone short vowel. Unfortunately, almost all Thai teachers and learners' dictionaries get this wrong. Material from AUA and the Union method do get it right. Don't believe me? Let me quote a couple of authorities: David Smyth in "Thai: An Essential Grammar" “When the vowel in the first syllable is -a ... in normal speech the tone is mid” James Higbie & Snee Thinsan in "Thai Reference Grammar" “In spoken Thai, unstressed syllables in multisyllable words maybe given mid tones in stead of the high, low or rising tone they should have according to Thai spelling. In this book the common spoken form is used, and these syllables are given mid tones.”

Download and Install the new font on your PC. Close Excel (if it's not already closed), then open Excel. The new font should now appear on the list. With thaifonts.org, most of the fonts are pirated, depriving their creators of revenue. A legal alternative is https://fonts.google.com/?subset=thai

Deleted (duplicate post)

Spot on! Thanks for alerting me to this. It looks like the fix I put in for "Reading Sentences" broke "Reading Words". Both should now be working correctly, though you may need to do Ctrl-F5 on the second page for each of these (but only the first time). The Reading Words second page does seem to be loading strangely slowly, so you may need to wait a few seconds to actually see the words.

Could you please post the console log for the first page, https://thai-notes.com/reading/lesson22.html That's where I believe the problem was. (That page passes data to the second page. It was the passing of data that had stopped working. The error on the second page which you've provided talks about "read properties of null". The data are null because they weren't passed from the first page. The log should look like this: ResponsiveVoice r1.8.3 responsivevoice.js?key=vh25OFgw:340 isHidden: false responsivevoice.js?key=vh25OFgw:341 Prerender: false responsivevoice.js?key=vh25OFgw:402 Configuring readloader-0.js:243 Version 1.3.0 responsivevoice.js?key=vh25OFgw:144 RV: Voice support read The key text is "Version 1.3.0". If it's missing, it's definitely a caching problem - either with your browser (most probable) or with your ISP (pretty unlikely, but possible). Incidentally, Incognito Mode does use caching, but the cache is cleared when you end the Incognito Mode session. May be worth closing your browser, reopening it and start another Incognito Mode session and trying again. Fingers crossed.

Not work in progress. They've been around for a few years. What I've done (and I should have done yesterday) is update the version number. When the page loads it's displayed briefly in the bottom left of the screen. (It's also written to the console log.) If this is displaying as 1.3.0, then I think everything should be working OK. (At least it works OK for me on the four browsers I've tested.) If it's less than this, then there's a problem with your browser cache. (Cloudflare is caching the correct version. I've checked.) As for "thanks to you and the others that have made this possible", the entire site (with the exception of the FSI language course) is all my own work.

TH SarabunPSK However, that information is not going to help you. It's not a font problem, it's an Adobe problem. Your best bet is to save the document as an image. (There are websites that will do .pdf to .jpg conversion for free.) Then upload the image to Google Drive and open the image with Google Docs.

It doesn't. It uses the web interface which is why it is opened in a new page. The text to be translated is part of the URL. Thanks for your concern.

The problem with the "Reading Sentences" pages in the Reading Course is now fixed. However, you may need to do a hard reload on the page with the "Read" buttons (not on the page that is opened when you click "Read" button). That's Ctrl+F5 in Chrome, Opera and Firefox and Option + Command + E in Safari.

Not sure what's changed. It's not immediately apparent what the problem is. I'll look into it.

Temporary glitch. Should be working now. Sorry about that.