Archive
Protected: LRC à la carte I: The teacher’s Vade mecum
Protected: LRC à la carte II: Choose from our start-of-term class inductions
How to sort a Pivot table by a calculated field column
How to work around flat flush-left nested lists in Windows Live Writer
- Windows Live Writer (2012), in WYSIWYG mode under the “edit” tab, conveniently interprets “tab” keys, when issued within an <ol>/<ul>, as, i.e. converts them into nested lists.
- However, Windows Live Writer does not horizontally indent the nested lists. Rather the lists appear “flat” flush left –(restart in ) only numbering and vertical indentation, like so:

- The underlying source code feature is that <li> get immediately closed, before the nested <ol> gets even opened, as you can see here:

- You can force the indented view by wrapping the <li></li> around the nested <ol></ol?, like so:

- The resulting look with horizontal indentation:

- Unfortunately, to make matters worse, certain work with lists in the “edit” mode make them revert back to the default “flat”view. So you often have to redo your work under the source code tab.
How to work around broken links and visible “Machine generated alternative text”issues with images from MS-OneNote in Windows Live Writer
- Problem: Sometimes when you use Windows Live Writer (2012) to post images copied from MS-OneNote (2010, 2013), the result (on WordPress) can get messed up, like so (post has since been fixed as described below):
- The image is missing (“src=” link broken).
- The “alt=” text is visible instead (and you did not want to post this “alt=”text anyway. (MS-OneNote OCRs images to make the text therein searchable; this text is put into the “alt”when pasting from MS-OneNote).
- Root cause:
- Windows Live Writer converts the pasted content by
- removing the “alt=”Machine generated alternative text: [deleted for brevity]”
- creating from the pasted content thumbnail images
- which it links in the “src=” tag, and links the thumbnail image to the full-size original image.
- If something – unclear what – prevents this conversion, Unfortunately, this is not obvious from the “edit” tab view or elsewhere within Windows Live Writer. But when posted, will result in “Machine generated alternative text” from MS-OneNote in place, but even break the image src link:
. - What exactly triggers (and would allow you to force) a successful conversion within Windows Live Writer I do not know. However, there is a simple:
- Windows Live Writer converts the pasted content by
- Workaround:
- After pasting your images, be patient : The trick seems to be to give Windows Live Writer enough time (more apparently if you have pasted multiple images) to finish
- Things you can look for in Windows Live Writer to make sure the conversion is finished:
- edit tab: you can tell the difference by the resizing of the image on the edit tab:
- source code tab: A somewhat radical solution, but here beneficial is that the conversion removes the imported “alt” text of the image.
- before: alt=”Machine generated alternative text: [deleted for brevity]” src=”$clip_image006.jpg”
- after: alt=”clip_image006″ src=”$clip_image006_thumb.jpg”
Digitales Wörterbuch der Deutschen Sprache dwds.de
If you can handle – or actually prefer the increased stimulus of – a monolingual dictionary resource, this one looks nice – with its parallel display of dictionary entries, etymology, common collocates, and empirical use in KWIK format – and well-founded: Based on the Wörterbuch der deutschen Gegenwartssprache (WDG) and providing access to many corpora that document empirical use (including frequency and longitudinal information) of the language – modern German, including spoken language and many newspapers, altogether comprising about 1.75 bn words.
MS-OneDrive “Get link” incompatible with MS-Word “Always create backup copy”, use MS-OneDrive versioning instead
- Symptoms:
- If I edit my local MS-OneDrive copy with MS-Word, my collaborators lose access to the most recent copy via the link I shared with them.
- Worse, the new file MS-Word generates when the backup is created, won’t get automatically synched with MS-OneDrive, and no sync error seems to get flagged in Explorer.
- Root cause (presumably):
- When saving in MS-Word, I can see my focus moving to the backup file
- MS-Word, when creating a backup of the original file, actually rather creates a “fore-up”: The original file gets renamed (“Backup of…”) and the recent changes get copied into a new file.
- The MS-OneDrive link keeps pointing to the old file “Backup of…”, “when after (which one can see normally, if the user renames a file manually, is a desirable feature)
- Workaround: I managed to manually upload the files that got out off synch.
- When saving in MS-Word, I can see my focus moving to the backup file
- Solution:
Practice Chinese Stroke Order at varying speeds
Here we are providing over 80,000 animated GIF files for you to practice Chinese Stroke Order at varying (hopefully increasing) speeds of your choice (millisecs denotes the time you have for each stroke): strip, 1010millisecs, 1000millisecs, 990millisecs, 980millisecs, 970millisecs, 960millisecs, 950millisecs, 940millisecs, 930millisecs, 920millisecs, 910millisecs, 900millisecs, 890millisecs, 880millisecs, 870millisecs, 860millisecs, 850millisecs, 840millisecs, 830millisecs, 820millisecs, 810millisecs, 800millisecs, 790millisecs, 780millisecs, 770millisecs, 760millisecs, 750millisecs, 740millisecs, 730millisecs, 720millisecs, 710millisecs, 700millisecs, 690millisecs, 680millisecs, 670millisecs, 660millisecs, 650millisecs, 640millisecs, 630millisecs, 620millisecs, 610millisecs, 600millisecs, 590millisecs, 580millisecs, 570millisecs, 560millisecs, 550millisecs, 540millisecs, 530millisecs, 520millisecs, 510millisecs, 500millisecs, 490millisecs, 480millisecs, 470millisecs, 460millisecs, 450millisecs, 440millisecs, 430millisecs, 420millisecs, 410millisecs, 400millisecs, 390millisecs, 380millisecs, 370millisecs, 360millisecs, 350millisecs, 340millisecs, 330millisecs, 320millisecs, 310millisecs, 300millisecs, 290millisecs, 280millisecs, 270millisecs, 260millisecs, 250millisecs, 240millisecs, 230millisecs, 220millisecs, 210millisecs, 200millisecs, 190millisecs, 180millisecs, 170millisecs, 160millisecs, 150millisecs, 140millisecs, 130millisecs, 120millisecs, 110millisecs, 100millisecs, 090millisecs, 080millisecs, 070millisecs, 060millisecs, 050millisecs, 040millisecs, 030millisecs, 020millisecs, 010millisecs. ![]()
Downloading the originals from the most helpful site (also available by direct download) created by Tim Xie for the California State University, Long Beach, and applying my bash shell script from here, then generating your own speed-differentiated versions, seems to difficult for most users. Even better, instead of perusing the above links, you could just hit my server once and download the whole lot of post-processed animated Gif files with different speeds from here.

