Hi everyone, Dave here…. A lot of users have asked for better traditional support so I’m happy to announce the beta release of a browser plugin that:
* works with Mozilla Firefox (versions 1.5 - 2.x)
* replaces simplified characters with traditional ones on the dialogue/expansion/vocabulary pages
* adds traditional character support to vocabulary lists/games/etc.
* replaces the link to the simplified PDF with the link to the traditional PDF
Things it won’t do:
* work with other browsers (without tweaking - see below)
* alter content you already have in your vocabulary list
* change Chinese text posted in comments, introductions, titles, ID3 tags, etc.
If you’re a Firefox user (downloadable here), you can grab the plugin by visiting this page. Installation is pretty easy. You need to (1) add Chinesepod to your list of plugin sources, (2) click on the link provided to install the plugin, and (3) restart your browser. The process identical to that for any other browser plugin.
Using another browser? This plugin is compiled from this Greasemonkey script. There are reasonably complete ports of Greasemonkey available for Opera and Safari. Feel free to let us know if you get the script working on unsupported browsers or come up with any cool variants or hacks.
On a closing note, it’s worth mentioning that traditional support is still in beta. This means that there may be errors here and there with word conversions, especially in the older PDF files. One issue I’m aware of is the handling of the word 甚麼 in some of the older PDF files. The academic team is making corrections of this sort on an ongoing basis and this particular issue will be resolved shortly. If you find any other errors in your explorations please drop a line.
It’s works well for what it does, but (alas) it’s an either/or proposition. There is no way to toggle between the two formats.
Not necessarily a problem, but people should probably be aware of that caveat.
Hope AuntySue will be able to make use of it, but not sure it’s conducive to her system.
Wow! Works great. Thank you very much for this plugin.
Dave
Simple to install. Thanks. Is there a reason it doesn’t work with the “Text Version” of the Dialogue? This of course would be nice for those of us that “Cut and Paste.
Mike
We’re linking to the simplified text file as there isn’t currently a traditional version being generated. When we add the traditional version we can regenerate the PDF files to fix the link. Hopefully by then we’ll have a way to access the text file without downloading the PDF as well.
FuDaWei
Yup… the browser plugin is an either/or choice. Greasemonkey can be toggled on/off so it is an option for anyone who wants to switch display options fairly often. Everyone seems pretty tech savvy, but the thinking here is that we should aim to keep the default installation as simple as possible.
It wouldn’t install for me yet, maybe I need to unblock some more stuff, but I want to say I’m feeling very skeptical.
What about nali and all the other li characters, how’s it gonna work them out? And what about all the characters that don’t seem to exist according to the computer, but look rather like the traditional character, like the wei4 and sui4 that have slightly different strokes on their tops in most conversion outputs? Can it get all that right?
I see two needs to be met.
When you’re learning to write the characters, you absolutely do not want to ever learn the wrong one with confidence. There is no room for forgiveness of errors, and wrong traditional characters aren’t as likely to be detected very often. So I want to be really sure it’s reliable before basing my learning on it, or, always check with a dictionary which is not much different from just having the pinyin after all.
Second, I have a purpose for the traditional characters which technically requires them to be reasonably correct. I convert all texts into Big5 format because that’s what my PDA understands. If there is one character in the file that is wrong, imperfect, or a simplified character snuck in, then the conversion fails. No hints as to why, it just fails. It could be one character, or fifty characters that’s making it bomb out, no way to tell.
Then what can I, as an ignorant learner, do to find and correct the character(s) responsible for this conversion failure? Nothing, because I don’t know the characters yet, indeed they are being collected because I don’t know them. Sometimes I can type in the dialogue myself and look for differences, but I won’t always spot them, and, well, it hasn’t helped me at all if I’m still typing everything myself has it
So, before I install it and give it a go, I’m letting you see how my final-product error tolerance is going to be pretty low, and yes I do know how very hard it is push something up beyond 95% of perfection. I wouldn’t be surprised, though, if you can pull it off.
Install time. Watch this space…
Good work Dave.
I would appreciate to hear how people will use V3 with simplified and traditional. What is the best way to study both forms together?
Second, Auntie referred to having the traditional script on her PDA. Would someone care to share how to get the pdfs visually on a MP3, and what needs to be done to have it in simplified and/or traditional? This is the first upswing that I have experienced with the changing to v3.
Thanks Dave.
AuntySue,
Part of the editing process includes a review of the traditional forms. This is one of the invisible changes that has taken place behind the scenes with V3 and is the reason for the expanded traditional presence in places like the review exercises and pdfs.
I looked at the problem before and seem to remember there being around 100 characters in the GB2312 character set with ambiguous fanti. Most ambiguities involve a very common character and a relatively obscure one. Software programs generally deal with the ambiguity either by making intelligent guesses based on word segmentation (Adso), or prodding the user for direction each time they encounter the character (Wenlin). There is the potential for human error in both cases and I don’t think either approach is ideal pedagogically. I’m biased towards the former out of the belief that pushing intelligence into software saves time and produces better results in the long-run.
Traditional support is beta and you will have to be the judge of whether it is useful given your study plans. I hope it ends up so, and feedback is always welcome even if not.
敦禮,
>> I would appreciate to hear how people will use V3 with
>> simplified and traditional. What is the best way to study
>> both forms together?
I’m not sure about the best way to study both forms in general, but one hack could be editing the Greasemonkey script to change only the popup text to traditional.
If the plugin is installed as a Greasemonkey extension this can be accomplished by deleting the following line:
result.snapshotItem(i).innerHTML = traditional;
–dave
Dave … Just out of curiosity, I assume you can control the font color attributes with your script. Would it maybe be advantageous to set any Traditional characters to (say) “maroon” or “dark blue”? That way, you could tell at a glance which mode you are in or which characters are being altered.
To display PDFs on a Palm PDA, and to do everything else you can think of for study on a PDA, look at some of the discussions on forum.chinesepod.com. Either do a search there for PDA, or find the longest of the PDA conversations by looking in the Forum Statistics page, it’s one of the most looked at topics ever. You will need to buy a piece of software to make the Chinese characters display though.
Greasemonkey can definitely change CSS styling.
We’ll be focusing more intently on mobile once the V3 transition settles down. We’re making progress but there’s still lots to do…. Figuring out how to make the PDFs or texts more easily accessible on PDAs is going to have to be part of that. And having access to all of the collected wisdom (!) in the forums is awesome - we’ll do what we can.
This is a great hands-on reference guide for learning how to use Greasemonkey:
http://diveintogreasemonkey.org/toc/
User scripting has bright future - it makes so much sense I can’t imagine future browsers not standardizing on supporting it. I really like the idea of changing the color of character where the traditional is different from the simplified.
@ AuntySue I can´t praise my beloved ChinesePera-kun enough ( the link: https://addons.mozilla.org/de/firefox/addon/3349 ). It doesn´t care about simplified or not is gives you the words and the meanings, so if there´s something wrong in the PDF you could check it with that little proggy (also it might take a while to go through the complete text that way) and you can toggle it on and off. The hook is that you have to do it with firefox.
hope you give it a try
excuter
What about tying the script to a button on the webpage? It would allow to switch back and forth between simplified and traditional without needing firefox plugin or greasemonkey script. The tooltip could contain both forms side by side (it would be great if it was a user option to choose to display simplified, traditional or both in the tooltip).
Peter, I’m with you. Having a conversion on the user end instead of traditional provided on the server end doesn’t seem like the real thing to me. Nor would it to them, I imagine, so there must be some very good reasons why they want to still provide only simplified and have us convert it from our end. Let’s go along with it for now and see how it pans out, because they seem to be implementing a lot of new and experimental stuff and some of it might work out well for us. We can always invoke the scream-of-experience later on.
Just checking: has anyone managed this with Safari yet? I had a look at the links above and it seemed… scary and way out of my depth.
And IS this the traditional support that’s coming, or is it a stop-gap measure? Ditto for the html version of the now non-copiable PDFs: is that just the way it’s going to be, or will the PDFs be cut and pastable again one day?
(I ask because I went through and scheduled lots of lessons today to get the traditional PDF delivered to my iTunes feed, and I suddenly felt really stupid when I realized I’ll want to do that all again should the PDF formatting be changed - as I hope it will be!)
With regards to the html transcript link (off-topic, but what the hey): it’d be nice if it’d be available straight from the lesson page; and I also wish it were tidied up a bit. The little formatting things: which lines are A:, which lines are B:, start sentences with a Capital Letter in the pinyin.
Would it be possible to get the Simplified/Tranditional pdfs back? Having to reboot to get either or, and having two transcripts floating around is rather frustrating.
V2 PDF headers and footers facilitated easy organization also.
I second 敦禮’s requests, if it does any good. Ever since PDF’s went to JUST simplified, apparently the encoding was changed. Now I can’t view them on my Nokia N70’s Acrobat Reader like I could the V2’s PDFs. Now when I view them on the phone it shows the ChinesePod logo and “Learn Chinese on your terms” but the rest of the 3-4 pages are blank. Why? And why the change if the PDFs before could hold both simplified and traditional?
I also really really liked having the traditional at the end so that after studying, after getting the dialog down and reading your English translation, I would use it as a test to see if I could translate it back in to English, both testing my memory as well as getting me familiar with traditional characters. Was there a big problem with having them both?
Apparently my phone’s PDF reader only can display unicode, and I haven’t found a way to add character sets to it like you can the Windows version. Please keep this in mind if there is any chance of going back to the old way… it was worth it and it made your paying customers happy.
-Rich
LostinAsia,
Expanded support for traditional can e found in the lesson exercises, as well as through plugins like this which switch display options and add traditional support to the flashcards, games, etc. The plugin is all we have on the display front now: user-side scripting is necessary to avoid placing a heavy load on the server and slowing the entire site down. Traditional character data is being distributed in the HTML source, so there is room for people to experiment with user-side scripting if they want to change the way any particular plugin works.
We’re getting a lot of positive feedback about the HTML files, so I’m expecting that we’ll simply keep them available as the preferred option for everyone who wants to copy and paste. We’re working on improving and streamlining the backend system which helps automate the production of all of this content, and improvements on what we have now are being put into that system. It makes more sense to focus on the next version of the production system and get it up sooner rather than spending a lot of time tweaking the existing system and delaying the shift.
I’m expecting that as the number of documents we distribute grows (additional files, audio materials, etc.) we’ll need to rethink how to make all of the materials more readily accessible.
敦禮,
The removal of simplified content from the previous PDF files was made to simplify the PDF and get rid of materials people were finding distracting. If you know the filename of the simplified PDF, you should be able to work out the filename of the traditional PDF. Editing the URL in your browser should be enough to get either version, regardless of whether you are using the plugin.
Rich,
Will keep your thoughts in mind, as well as all of the other feedback on this thread.
When I click on the link provided for the Traditional plugin the page comes up with the following message:
Error 404 - Not Found
The page you requested was not found.
What’s up with that? Has the link changed?
I’m having the same problem as Bismarck3005. Does anyone know whether the link for the Traditional plugin has changed?