Quote from Vadim on January 11, 2021, 6:54 pm

The vlWord plugin was created to work with MS Word documents from VisualNEO Win (NeoBook) projects.
Creating .docx (including .dotx template), editing .docx, .rtf. Converting them into .docx, .rtf, .pdf, html files. MS Word must be installed (the plugin uses it as an automation server).

The plugin is free and will always be free for everyone.
Nevertheless, I will be glad to get some coins on my PayPal: https://paypal.me/vadimlevkin

Now you can save the results of any of your programs directly into an MS Word file. Or, for example, you can make a program that will process the contents of the file (do formatting, auto-replacement in it or something else). At the moment, the plugin has 101 commands. Among already available commands are file management, page display mode, font formatting, work with bookmarks, tables, creating frequency dictionary of words used in file, writing to file, reading from file, etc.

Plugin moved into open alpha-testing mode. I invite you to participate in testing!
This means, that you have to install the plugin, use it, find some bugs and inform me in this thread :)
Before you decide that a bug is found, please read the description of the command in the helper window or in the RTF file of the same name in the Loc folder. Also, check if the command works when VisualNEO Win (NeoBook) is launched with administrator privileges (it is always better to use the "as administrator" mode to launch VisualNEO Win or NeoBook since it is a development environment, not just an application program).
I am grateful in advance for all bugs found, including translation flaws.

The plugin doesn't work with any active MS Word documents, but only with those opened with the vlWord plugin or opened through that MS Word window which is opened with the vlWord plugin. For example, if you opened a file with the vlOpenFileWord plugin command, and then the user manually opened another file in the same window, he would be able to work with the plugin commands in that new file. If you run another instance of MS Word (for example, by opening a document through Windows Explorer), then the plugin will not have access to that document.

Each command in the plug-in has its own RTF help file, which is displayed in the command setup assistant window (in VisualNEO Win or in NeoBook). Thus two purposes are achieved at once: 1) no need to study the help - all information about the command is in the assistant window of the desired command (with so many commands this is relevant), 2) the file can be easily translated into any language (the plugin window supports Unicode, so you can translate RTF files and localization file into any language), which makes the plugin open to the whole world.

I used Google Translate (through https://www.onlinedoctranslator.com/ru/translationform) to translate RTF files from Russian into Spanish and English, and now I hope to get help from native speakers in correcting texts. The localization file - vlWord.loc - has been translated into 25 languages in the same way. If you notice any mistakes or inaccuracies, I ask you to correct the file and attach it to the post in this thread. This way everyone will see the progress in improving the commands description and understand what is not done yet.

Writings in the windows of the assistant commands are taken from the localization file - vlWord.loc, which as well (as well as files RTF) can be translated into any language. The only thing left in the localization files, that I translated, are the strings which are displayed in VisualNEO Win (NeoBook) itself - these are the prompts which are visible in the command selector when you hover your mouse over the command name in the command list (unfortunately Unicode is not supported there, but it's OK, because Unicode is supported in the helper window). For this reason, leave lines 145-258 and 260 in English in the localization file (Russian will be displayed correctly, it does not need localization file at all).

Pay attention to the paths to install (place) the plugin. They are important for the RTF files and the localization file will be displayed in the assistant window.

Before installation, please read the file vlWord_Readme.rtf, which describes the procedure of plugin installation.

The plugin comes with a demo project vlWord--Demo--RU.pub. And for Spanish and English versions - vlWord--Demo--EN.pub. When you test compile automatically opens the file 123.docx (for your experiments). This file must be located in the same folder as the demo project. You can disable the command to open this file in the Startup tab of the Project Properties. Use the main menu to navigate between commands while running the demo file. The order of the commands in the main menu corresponds to their order in the plugin.

All commands in the plugin are added to the NeoCommands database. This means that you can quickly find the right command by sense. There is already a web version of NeoCommands in English, available on my online course in the Help section. The link to the course is: https://distant.orgpsiholog.ru/course/view.php?id=20

Download the archive with the current version of the plugin at the link below. After unpacking the plugin, check the paths to it, if necessary, rename the folder with the plugin, as described in the file vlWord_Readme.rtf.

Plugin in Russian (vlWord_RU.zip): https://yadi.sk/d/8JgwxYG0P-RKAw

Plugin in Spanish (vlWord_ES.zip): https://yadi.sk/d/34CbFtr934uB8A

English language plugin (vlWord_EN.zip): https://yadi.sk/d/nF1Cf046TWDcXQ

Localization files for other languages (vlWord_Loc25.zip): https://yadi.sk/d/4uOHAKy9TttQ8Q
(af, ar, az, be, bg, cs, de, el, en, es, fa, fr, hi, hr, hu, it, ja, nl, no, pl, pt, sv, uk, zh-ch, zh-tw)

 

Big thanks to Andrei Solodyankin, who taught me how to build plugins in Delphi and helped me to solve difficulties during the whole process of making this plugin!

 

P.S.: I wanted to please the forum users by the New Year... let's consider that I made it! :)
Happy New Year, my friends!