Midsummer's Day 2020
It's a good point. We replied:I understand that installing v6 and v5.5 both need “Run as Administrator”. I did that with Version 6, and it produced no error messages. But I cannot locate the programme on my computer
which seemed to do the trick.To locate Scientific WorkPlace v6.0 (we’re assuming you’re using Windows 10): if there is not a SWP6.0 program icon already on the desktop, click on Start and scroll down the alphabetical list of programs. Click on Scientific WorkPlace to open the dropdown, and you will see SWP6.0... <snip>
Why not right-click and pin to the Start menu so as to find it more easily again next time? (And from there you can drag it to the desktop, if you wish.)
We drew attention to the fact that, as an Annual Maintenance site, they had complimentary access to the videos of our v5.5 Training Course and suggested the relevant topics they would particularly benefit from watching.Firstly, let’s not get confused between the additional files required for the:
- Typesetting specifications (class file .cls, class options .clo and packages [previously known as style files] .sty) these are all very important – Step One of https://www.mackichan.com/index.html?techtalk/421.htm, and
- Onscreen appearance when editing the document (confusingly also called style files .cst) these are relatively unimportant – Step Five of https://www.mackichan.com/index.html?techtalk/421.htm
You should proceed as follows (Note that Nos. 1, 2 & 4 are one-time only; No. 3 might need repeating every time the document is exchanged with a co-author using Texmaker):
- Put the class file [classname].cls in C:\swp55\TCITeX\TeX\LaTeX\contrib\[classname]\ (which folder you will need to create)
- Make a copy of the screen appearance file C:\swp55\Styles\article\article.cst and put it in C:\swp55\Styles\[classname]\ (which folder you will need to create) as C:\swp55\Styles\[classname]\article.cst. (This step is optional, as Scientific WorkPlace will easily use another .cst file if this file is not present)
- In Scientific WorkPlace, use File – Import Non-SWP/SW LaTeX to import the document [filename].tex; save it as [filename]-mod.tex (for example)Apologies, but: at this point there is an anomaly/bug, bearing in mind that LaTeX uses \ to denote a command. You will need to open the new file [filename]-mod.tex with WordPad, find the two lines\input C:halfway down the first page, and change to the single line
\swp55\Test\[filename]-defs.tex [or similar]\input C:/swp55/Test/[filename]-defs.tex [or similar]MacKichan Software have commented:
Looks like a bug in the input filter on how \def statements in a document preamble are handled. Probably not noticed before as \def is plain TeX rather than LaTeX so not commonly used in the preamble of LaTeX documents.
Changing the \def statements to \newcommand or \renewcommand as appropriate seems to get rid of the \input statement
- You can now open [filename]-mod.tex in Scientific WorkPlace. When compiling, we recommend you don’t just ‘Return’ past the information messages – note what they are telling you: the document requires multirow.sty, and threeparttable.sty. The co-author should have let the user have these packages along with [classname].cls; alternatively you could Google them and download them. But I’ll save you the effort; simply save these two .sty files (attached) in C:\swp55\TCITeX\TeX\LaTeX\contrib\[classname]\ along with [classname].cls.
The document will now compile to produce the PDF attached...
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.