Leap Year's Day 2020
We replied:...you provide on page 360 Appendix B Keyboard Shortcuts a useful summary of shortcuts. But substituting control s for command s does not work: I tried to insert a sum with the keyboard sequence "command s followed by s", command s immediately induces a save command! Any get arounds for this?
We hope this will of interest to others too.
- ...on p362 it says the commands for a Greek letter sigma is Ctrl-g followed by s or S (for lowercase or uppercase sigma). This is till true in v6.0, with the change from Ctrl to Cmd. So on the Mac, Cmd-g followed by s or S gives you the Greek letter sigma; you said "I tried to insert a sum with the keyboard sequence 'command s followed by s'", but any command starting Ctrl-s or Cmd-s is going to trigger the Windows or Mac commands to save the document. Similarly, Ctrl-i or Cmd-i gives an integral
- Note that the Greek letters entered as above do not resize when put in a Display (as distinct from the summation operator)
- If you want the summation operator sigma, then you should use either:
- From the mouse, point and click at the sigma on the Math toolbar (View – Toolbars – Math toolbar)
- With the keyboard, enter Ctrl-spacebar (NOT Cmd-spacebar) to bring up the Macro dialog at the bottom left of the screen, and type sum (followed by Carriage Return)
- Another option would be to save your own operators or characters as fragments; calling them back is quite efficient if you give them short two- or three-letter names. See our video 2h-Fragments <snip>; the second half of the video discusses how to create your own fragments. These videos were recorded on a Mac
- We also recommend you download the version 6.0 copy of Creating Documents from our manuals page and work through Chapter 5 (p67)
You would certainly expect so, wouldn't you... But because v6.0 is a complete re-writing of the code (whereas v2.0 to v5.5 were all bolt-ons to the original v1.0 code base), here's the answer we actually gave:
One question will 5.5 files run on version 6?
Clearly, all our v6.0 users have done this transition, but it's the issue about which we get some real dissatisfaction with v6.0.
Let me give you a thorough answer to v5.5 files running on v6.0:
- In theory, of course, the answer is Yes
- Any issues arise from the fact that v5.5's file format is .tex; whereas for v6.0 – to incorporate the new functionality – the file format is a .sci folder which contains a tex file
- We covered this issue most recently in our September 2019 mailing Item 3
- Files are brought from v5.5 into v6.0 using File – Import TeX, and exported from v6.0 to v5.5 using File – Export TeX
- For straight-forward documents there are no problems. But the reality is that complicated v5.5 documents (especially those which started life as hand-written LaTeX imported in to v5.5 rather than being created by Scientific Word/WorkPlace) can cause problems
- While the v6.0 import/export is pretty good, you would ideally only want to do it once when you upgrade from v5.5 to v6.0. You wouldn't want to be working on the same document, sometimes with v5.5 and sometimes with v6.0. Ideally, co-authors should be using the same version of Scientific Word/WorkPlace.
package bezos not present in repositorycame up when a user newly installed v6.0.30 on a MacOS 10.14.3 (so not the Catalina problem). He asked:
The answer is that Yes, you should be concerned about any error message during installation. We wrote:During installation an error message appeared - I attach a screenshot. Should I be concerned about this?
But we were wrong: his system was working fine. We forwarded the issue of the missing bezos package/s to MacKichan Software, and they responded:I'm supposing your Scientific WorkPlace will not work on account of this error, but it's worth testing it.
- At Step 8 do you get the gold seal?
- Try opening a new document (eg. File – New – Standard LaTeX – Standard LaTeX Article) and compiling (PDF preview at the bottom of the screen, or Cmd – Shift – P). Assuming it doesn't work, please let us have the log file: our instructions for this (December 2019 mailing Item 7) are written for Windows, but it's similar on the Mac: the log file will be in Documents/SWPDocs/[filename]_work/tex/main.log
In this case, it wasn't a problem.Yes, that's the case. I've made appropriate changes that will appear in the future, but I don't know what that schedule will be. This is caused by changes on CTAN...
The packages from bezos that we were using are accents and dotlessi.
Version 5.5 Tech Support – retired in June 2017 – is still readily available to our Annual Maintenance and Support Contract sites, and we offered them these two options:We're encountering an issue with a new user regarding their licence [on 5.5]
I've attached a screenshot of the unlock page they're seeing. Are we able to manually licence, as per the attached?
- Easy Option: We can supply the v5.5 licence file license.lic for you to save in c:\sw55\Licenses. This is specific to the computer in question, and so we need you to provide us with the computer ID as well as the serial number of the program. To obtain the computer ID, go into Scientific Word and (for v5.5) click on Help – System Features. The computer ID is in the System box.
- Better (independent) Option: Go to http://licensing.mackichan.com/Activate from any web browser and enter the required details (only Scientific Word; 5.5; computer ID; Serial number; Email address are required) to obtain the licence file both in the browser window and by Email. Please see our February 2014 mailing Item 2: don't include a British English serial number. You'll get the licence information between asterisks, eg.
FEATURE SW mackichn 5.5 permanent uncounted \
HOSTID=COMPUTER_ID=a1b2c3d4 TS_OK SIGN="0037 5903 2A7C 0F13 \
44E4 1D18 3F5C 1E00 06DD BB92 B4D3 0F2F B3BB CFD9 F737"
FEATURE British_English mackichn 5.5 permanent uncounted \
HOSTID=COMPUTER_ID=a1b2c3d4 TS_OK SIGN="0017 6F4C 1DF5 8F0C \
E96F 572D A985 5300 02AE 679F 7E0D 1A32 2040 EFA0 EFA3"
And you can then either:
- Save the text between the asterisks (including the blank line before the final asterisks) to a file called license.lic (Note the American spelling) and put it in c:\sw55\Licenses. To create file called license.lic with NotePad it's easiest to start by copying and editing an existing license.lic from another computer, or copy-and-rename packages.lic from the same folder; or
- Type the 15 blocks of 4 characters (highlighted [the characters generated for your computer ID]) into the 15 spaces at "Unlock code" (and repeat with the 15 blocks of 4 characters for the British English spell checker, if the serial number had previously been linked with the British English dictionary)
And, in order that his trial of v6.0 had not been wasted time, we suggested he export any work written in v6.0 to .tex using File – Export TeX (in v6.0), and then open the .tex file in v5.5 before copy-and-pasting into his preferred v5.5 document shell.To move your v5.5 setup to a new computer you will certainly need to reinstall and Register. You will also want to read the following mailings:
Once the British English dictionary is installed on your new computer according to the installation instructions, you can transfer the words saved in your personal list by copying across the file c:\swp55\brtuser.clm; the additional words for the American English dictionary are in c:\swp55\enguser.clm.
- August 2013 mailing Item 2 (Transferring to a new computer)
- February 2014 mailing Item 2 (British English dictionary, when Registering v5.5 on a new computer)
- February 2015 mailing Item 5 (Making the new installation look like the previous computer)
MacKichan Software responded with:Is there a plan to certify SWP for s level security on Win10?
We don't envisage that changing. But if it does, this bi-monthly mailing is the place you'll hear it from us first!
Windows S requires that applications are available via the Microsoft Store. We do not, and do not currently anticipate, being available via the Microsoft Store.
As far as I know, our products, or TeX Live or MiKTeX, cannot be used with Windows S.
This software is way too good to keep to yourself! Why not tell your colleagues and co-authors? Perhaps some Emails... maybe a blog post on a mathematics/economics forum? Even easier is to Share our Facebook page – or any of the Product pages on our website – with your Facebook friends. Thanks a lot.