silnrsi / silconverters Goto Github PK

Both installers, when looking at the options for SILConverters for Office, seems to indicate supporting 2016/2019/365. This indication is both in the small explanation screen on the right of the installer, and in the menu option (you need to scroll to the right or use the hover over tooltip) to see all the text of the menu option. @bobeaton says it should support Office back to 2003. If so, can the installer text be improved? Below are two screen shots (the filename, showing the bitness, is below the images)

Sil_converters_for_office_x86.png

Sil_converters_for_office_x64.png

If the installer does not match the bitness of Office, then there seems to be two entries

• SILConverters for Office 2013
• SILConverters for Office 2016/2019/365

not just one

• SILConverters for Office 2016/2019/365

I did a Zoom call with someone who was having trouble with the converter.

First of all we had to uninstall SIL Converters 3.1, then SIL Converters 5.0, then SIL Converters 5.0.0. I think we did it in that order and she did have to reboot once or twice in there.

She is on Windows 8.1 and using Office 365 and it's 64bit.

We installed the newest SIL Converters 5.0 from October 13 (SIL Converters x64 installer (for 64-bit Office) 5.0).

Then we opened Word and went to the Addins and tried to add the converter from there and got the attached error message.

I don't know what that means or how to get around it.

I had her close Word and then we reopened it as "Administrator" and got the same error message.

But, in the end, we used the Bulk Word Converter and we could add the converter through that way. The Bulk Converter worked fine. Then we opened a doc in Word and another in Publisher and the converter that we had just added worked fine, so the problem was just in Add ins. Then, I asked her to go back to Add ins and try adding another converter and we got the same message.

Anyway, she's functional now since she doesn't think she'll need to add more converters, but I wondered if this was a bug anyone else encountered and if there is a known solution.

A user reported an issue by sending the screen shot below.

Currently Python 2.x can be used to write a converter. As Python 2.x is no longer supported, it would be nice to move to Python 3.x at some point.

Quotes from an email:

The "Uni-consistent-spellchecker" won't allow you to use arrow keys in Word. Can the uni-consistent-arrow-key-blocker be removed, fixed, or at least made a non-default option in the installer in the next release?

With that "shortcut" we saved a few people some keystrokes, but ended up hamstringing the rest of the population!

The installers for SIL Converters v5.1 (released in January) do not seem to be signed. These installers are build with GitHub Actions, and I thought signed by TeamCity.

When TECkit mapping editor creates a new file, it places the following two lines at the end of the preamble:

Left-hand range = 0000-007F
Right-hand range = 0000-007F

This causes compiler errors:

unexpected identifier: "Left" at line 8
unexpected identifier: "Right" at line 9

until these lines are commented out.

It seems that these are items used by the editor itself and should be commented out along with other items in the preamble.

Both installers, when looking at the options for Bulk Word Document Converter , seems to indicate supporting only though 2013. This indication is both in the small explanation screen on the right of the installer, and in the menu option (you need to scroll to the right or use the hover over tooltip) to see all the text of the menu option. @bobeaton says I’ll test this, but it should support any version from 2003 (or 2016++ if x64 is installed). If so, can the installer text be improved? Below are two screen shots (the filename, showing the bitness, is below the images)

Bulk_word_document_converter_x86.png

Bulk_word_document_converter_x64.png

The installer will check for the bitness of Office, and if there is a mismatch (say 32 installer and 64 bit Office), the install option SIL Converters for Office will be un-selected. That is good. If I select that option anyway, the installer seems to complete. I presume that feature will not work. Is that ability to override intentional?

The version number for this release is 5.0, yet when using the installer the number 5.0.0.1 flashes briefly on the screen. Where does this number come from?