User:Acunning40/quiz

This is where I'll collect suggestions that people are making in the discussion about the new proofing quizzes. The quizzes are here at the test site.

Crossed-off items have been changed in my sandbox.

General, miscellaneous

• Have separate threads for Greek & formatting quizzes (programming is done; forum threads just need to be created and urls inserted into pinc/quizzes.inc)
• archiving:
  • separate archive threads, one for each of the main threads?
  • keep using the current archive thread for formatting quiz or not?
• forumpost:429124: in the 1st differing line message, identify which is expected & which is user's text. (See also forumpost:429173 and PM received 2/24.)
• forumpost:431230: allow image resize in the quizzes
• forumpost:431230: allow WordCheck in the quizzes
• change the wording of the message that links to the forum thread, to make it clear you should go there for any help not just to report technical problems. Perhaps "The algorithm for finding errors in this quiz is a quite simple one. To ask for help or report a problem with this quiz, please post in this forum topic. (For quickest help, include a copy of your corrected quiz text and the error message you received.)"
• consider use of file_exists() for tutorials. Any advantage to adding a tutorial filename to the definition of a quiz rather than looking for the presence of a file?

Tutorials

• forumpost:338121: maybe too easy/obvious to have tutorial right before taking quiz; maybe not an issue for Basic but could be for other levels that might be used for round access
• forumpost:339074: change "Continue" link to something more specific: "Continue to quiz"?
• forumpost:339458: require the tutorial, rather than having the option of tutorial or quiz

All quizzes

• forumpost:338167: reword scanno message
• forumpost:410646: on the last page of a quiz, provide links to start another quiz (not requiring the user to return to the proofing quiz home page before going on to the next one)

Basic Quiz

• carry over the hints from the existing quiz
• see if any other messages need hints

Page 2

• forumpost:338405: change message for spaced long dash

Page 3

• add some messages in case the user changes the case or otherwise alters the chapter header

Page 5

• change something about the ellipsis (it's now in the middle of the quote not at the end)

Moderate Quiz

Page 1

• forumpost:378963: allow eye-*bearing

Page 3

• forumpost:379132: have the preformatting mask an extra or missing space

Page 5

• will need to change the handy fact at next guidelines revision. Maybe should just replace the fact now?

Greek Transliteration Quiz

• forumpost:424093: have one of the iota subscripts already transcribed as 'i', so user has to remove it
• forumpost:429187: allow punctuation on either side of the ]

Access, qualifications, etc.

• forumpost:339350: hide, restrict, or otherwise discourage newbies from taking the F quiz
  • now on its own page--might be enough?

Code Status

To-do list (in no particular order):

• go through and apply _() everywhere that needs it (mostly done as of 8/22/09, but need to deal with the wizard and the tutorials)
  • June 3, 2010: the wizard is now in pretty good shape. Still working on the tutorials, about 1/4 done so far
  • June 4, 2010: Tutorials done too
• trigger all error messages: check for proper recognition, guideline link, wording, appearance, etc.
• set sandbox to UTF-8, trigger all messages related to non-ASCII characters under on different OSes
• set sandbox to Latin-1, trigger all messages related to non-ASCII characters from Mac & Linux
• get Michael to review handling of encoding issues

Log:

• October 1, 2008: conversation with cpeel in Jabber pgdpdev room, he suggested saving quizzes in utf-8 format and converting user input to that. I tried it out using his supplied code and got it to work. He also said that he wasn't sure that would be a good way to go and he'd want to talk to Michael about it.
• June 14, 2009: adjusted error checks for œ/†/‡ in user input, which weren't being detected correctly in a Latin-1 site encoding (since they're not in Latin-1, they weren't getting converted properly to utf-8.) Seems to be working now, but the method may or may not be a good one to use....
  • did some tests across different browsers and OS's (still need to have somebody do the test on a Mac though)
  • need to adjust the error checks based on the testing, specifically using chr() vs. actual character vs. HTML entity under the appropriate circumstances