Printed on thermal paper and scanned (and post-processed in ImageJ to tidy it up, but only a little). Includes some Greek, a good set of math symbols, accented characters, including the ability to put any accent on any letter, some fractions, degree/minute/second symbols, paragraph marks (pilcrow, is it?). Pre-dates euro, of course, otherwise pretty useful.
This is the second of two posts on the topic. The other is here.
(1) Open the template (.dotx file) in Word as if it were a document.
(2) Find an example of the type of thing you want to change (in this case, level 3 entry in the table of contents).
(3) Open the Styles pane.
(4) In the styles pane, right click on the style you want to change. Select ‘All instances’.
(5) In the styles pane, right click on the style you want to change. Select ‘Modify’.
(6) If you want to fix the ToC as noted in the previous post, see that post to see what you need to change. If you want to change other aspects of the template, I’m sure you can work that out.
(7) Save the changes and close the file.
(8) Open the word file and attach the template (see previous post), and styles should update. If not, check ‘Automatically update document styles’ when attaching the new template. Once the fix works, you may then want to reattach it without checking that box so that styles don’t get accidentally modified.
This is the first of two posts; other is here.
So I’ve got a Word file with a table of contents (ToC) that, every so often, is missing the dot leader (row of dots) between name and page number. Like this:
Now, I checked that this is not just a display problem, and yes it does print like that too. The ToC was put in using Word defaults with the headings all styled as H1, H2, H3. Nothing out of the ordinary.
So of course I did a web search and found: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_word-mso_other/dot-leader-sporadically-missing-from-table-of/78038ac4-4df2-46a7-93c6-4939ef3056d2?auth=1 (hence the title of this post of mine).
But this page does not give an explicit fix, at least, not for the average user. But it does give the hint – note that the entries that are not working are short. For example, I can change ‘Mode’ to ‘Mode Mode’ and it is ‘fixed’:
So the simplest solution is to rephrase the headings to be a little longer. Easy but suboptimal. Note that putting it back to just ‘Mode’ and updating the table recreates the error.
Here is the solution (at least in my context).
(1) On the Home ribbon, expand the list of Styles by clicking on the little arrow at the bottom right of the styles pane.
(2) Then Go to TOC 3 in the Styles list
(3) Right click and select ‘Select All Instances’
(4) Right click and select ‘Modify’
(5) Select ‘Format’
(6) Select ‘Paragraph…’
(7) Change ‘Hanging’ indent to ‘(none)’
(7) On the same dialog, select ‘Tabs…’ (bottom left corner).
(8) Highlight the first tab stop (there will likely be two) and delete it by selecting ‘Clear’. There should now only be one tab stop, that giving the page number position (15.9 cm in the picture here).
(9) Make sure the button beside ‘2 …..’ is checked. Then OK all the way out and bingo, fixed.
(10) Caveats: I don’t know how this solution might interact with other ToC styles and formats. It worked for me, YMMV. Also, if the change is not saved back to the template (ie, this change is made permanent) then when the file is reopened and attaches the template, it will revert to the faulty version. Solution is to either do a manual fix each time (or at least each time you want to print the document) or to make a custom template and attach that.
The latter is better. The simplest thing is to find the template you are using (File → Options → Add-ins → Manage: [Select ‘Templates’ from the dropdown menu] then click OK and the template and its path will appear in a little text box in the dialog that comes up) and then find it in your file manager and make a local copy of it, either in your personal Templates folder or in the same directory as the Word .docx file you are working on, depending on whether the change is just for this document or for all future documents. Then use the ‘Attach…’ button beside the name of the template to browse for your copy of the template.
That will attach the copy to the Word file. Then do the changes noted above, but with one addition: The change will be stored to the template if you select ‘New documents based on this template’ in the ‘Modify Style’ pane. When you close the Word document, Word will/should ask you if you want to save changes to the template. Or, at least, that’s how it looks.
Alternatively, see post ‘Changing a Word template to fix the dot leaders in the ToC‘.
Went to save an annotated document in Acrobat Reader DC (on Win 7) and got a blank dialogue box:
Thought it might be to do with the comments, but it’s actually to do with Adobe’s obsession with driving custom online — fortunately, the fix is simple:
Edit → Preferences → General
and deselect anything to do with online storage — in the case below, it is ‘Show online storage when saving files’:
Voila (as they say, which is odd ‘cos I thought it was a cross between a violin and a tuba).
You can work this out yourself, but a blog is always in need to content…
Notepad++ is an excellent Windows editor.
The dictionaries with which it is installed seem to live in:
(maybe Program Files x86 on some machines). The local ones are expected to be in:
if you do a conventional install, or the the Program Files directory if a USB-type install.
To add one, Plugins → DSpellCheck → Settings
I clicked Download Dictionaries, but it could not connect to any of the suggested servers. (‘Status: Can’t list directory files’; computer is accessing internet no worries, so that’s not the problem.
Dictionaries have names like ‘en_US.dic’, and are Hunspell ones. First, looked around on my computer to see if some other application had already downloaded them. LibreOffice, that sort of thing.
OK, no luck. Went back to the Download Dictionaries dialog and copied the address it was going to for dictionaries:
Yes, opened OK in browser.
Saved en_AU.zip to:
unzipped it; made sure the files were in the Hunspell directory, not a subdir of it.
Then back in notepadd++ Plugins → DSpellCheck → Settings
Clicked on ‘Language:” and the dropdown had AU in there as well; selected it.
32-bit Win 7 VirtualBox virtual machine (VM) running atop Linux (Debian Old Stable, 7.11). VirtualBox version 5.1.30.
Boots fine, behaves well… here is the resulting desktop, captured using Host-E:
Now, to get full screen, I hit ‘Host-F’ where the Host key is usually right Control. Here’s what happens when I do that (grabbed this screen using Gimp, since Host-E gave an image identical to the above, which was not what I actually saw):
Now, if we look more closely at the second image, we can see a cursor (near the top):
What seems to have happened is that the narrow border around the screen, drawn I think by VirtualBox itself, is covering the VM screen. Since VB is drawing the border itself, and knows it is a border and not the VM screen, presumably it doesn’t capture it when Host-E is used to grab the screenshot, which is why the Host-E screenshot actually looks OK — even though the user (me in this case) can’t see anything! But Gimp captured what was really there.
Now, the fix is easy — use the four-pointed cursor (yours may look different) to resize the bottom border by clicking and dragging it all the way to the bottom of the screen:
So I guess this counts as a minor bug in VirtualBox, but not much of an issue. So now that’s sorted out I can get on with some editing.
I like crgrep. Now, grep is a great tool, very useful for people who deal with documents. But many editors spend a lot of time in GUI environments, using products like Word and Acrobat. Nothing wrong with that. But there are some great command line tools. crgrep is useful because it can search through Word files, which are not plain text but highly formatted XMLish things that a lot of regular command line tools cannot cope with. And it can search through whole rafts of files at once, PDFs, docx, xlsx, and so on. There are some things, like catdoc, that can be used to convert Word to plain text, but that turns the searching into a multistep process (yes, it can be wrapped up in a script).
crgrep is nice because you can get quite a lot done without becoming too much of an expert. Thus, a simple example:
Let’s say I want to know how my colleagues have been formatting a term like “4–5 year olds”. Where are they using hyphens? I know that the edited versions are in directories of the form
and I want to look at how things have been done in multiple projects.
I can open my command window (I am using Windows 10) and cd to the directory from which all the ProjectName directories grow. I can type:
C:\Folder> crgrep -r --colour=always "5?year?olds" *\Edits\*SET*.docx
And I will get a list of all the occurrences of ‘5-year-olds’, ‘5-year olds’, ‘5 year olds’ etc in all the files that are Word docx files that have been designated as ready for typeSETting (ie the editing is completed). Now, systematic file naming helps, but crgrep is most useful here. I can search in docx, PDF, all, whatever. Very useful indeed.
I’ll parse the command, since this post is for the editor not the computery type.
I am in the Folder where the project subdirectories come off, hence the prompt looks like C:\Folder>.
I have already installed crgrep, so I type the name of the command. ‘-r’ tells it to recursively search through the file structure (ie look in subdirectories). ‘–colour=always’ tells it to colour any text that matches my pattern. Then I give the pattern, enclosed in double quotes. Question mark just means ‘any one character’. Then I specify where to search (I do not need to be in C:\Folder> for this to work, as long as I specify the path correctly). The first star (*) says ‘anything’, so it’ll look in all subfolders. But once inside a subfolder, only look in folders called ‘Edits’ (there’s one inside each project subfolder) and then the last bit says only look at docx files that have SET in the name.
This overall command structure solves a large fraction of the searches I need to do.
Now, I actually know how this term should look, but there is a lot of variation in things like hyphenation and preferred usage of some terms between clients, and some of it is captured in a style sheet but some is not, and this is a useful way of seeing what is actually happening.
Addendum: If the Windows command line is of interest but now PowerShell, a really great tool is Clink. It makes the Windows CMD.EXE command line almost as usable as say bash, by using the readline library for command completing and recalling history between sessions.
Install of EndNote X7 on Windows 10. A few notes
(1) Downloaded the installer from https://support.clarivate.com/Endnote/s/article/EndNote-Installer-download?language=en_US
(2) Double clicked on it, entered appropriate product keys
(3) Locked up on the screen ‘Installing Direct Export Helper’
(4) Had to use Task Manager to kill installer, but then second attempt complained an installer was running, so rebooted computer
(5) googled; found http://www.adeptscience.co.uk/kb/article/138C2
(6) Did what it says, namely:
a. Selected custom install when installer asked and unchecked Install Direct Export Helper (see red arrow on picture)
b. Proceeded through install; no worries. Let it finish
c. But then went to C:\Program Files (x86)\EndNote X7 and Risxtd.exe was not there. So could not install the Helper separately, as the instructions said I should
(8) Downloaded Risxtd.exe, copied it into C:\Program Files (x86)\EndNote X7 and ran it
(9) All fine
Whether it relates to compatibility with version of Windows newer than the program, I don’t know. I can confirm that setting the compatibility level to Windows XP SP 3 (recommended by Windows compatibility wizard) did no good.
This is a reminder to me. Please ignore.
The other weeks I wrote this post. I noted that the recommended solution threw the baby out with the bathwater.
Here I just note that the error that comes up when converting to unformatted citations was overcome by running the conversion on the whole document (Ctrl-A then run the command) and then after it threw the error finding where it had got up to, highlighting unconverted entries one by one and converting individually (or a paragraph at a time), and then trying the whole document conversation again. One of the entries must have been the troublesome one, because after doing this a couple of times the process made no errors and converted the whole document. So the problem appeared to be a field or a bit of formatting created by EndNote itself, though it is possible there was a custom style that EndNote did not like and by selecting just the citation it was able to cope.
Now, something I like about EndNote: An easy way to put special characters into entries is to copy them from Word and paste into EndNote. For example, most bibliography styles recommend using an en rule (–) (often called en dash) to give a range, as in a page range like 234–312. If you stick an en dash into the page range in EndNote, it does make its way into the formatted bibliography. A simple thing, but a good thing.