I may give this a try. But it took so much trouble to get wine installed and working - and I need wine for the work I'm doing - that I would rather wait and update the current system than start over. Will await developments!
Ah - I see about Flathub. It would have been nice if a message appeared that explained what happened, but now I understand. And I understand about the problems with Luakit. Nothing I do can get the browser to go past the "10%" message as it tries to load any site at all - and this happens in the text-based version as well as the gui version. But of course I can manage without any of these things until the new version arrives. A text-based browser! It prompted me to see if Lynx is in your distro,...
I followed your directions exactly, and the Flat Hub button disappeared from my Peppermint Hub! There is now a blank space beneath App Image Hub. How can I get the button back? Also, the App Image Hub still produces an empty window. But the other buttons work correctly.
I followed your directions exactly, and the Flat Hub button disappeared from my Peppermint Hub! There is now a blank space beneath App Image Hub. How can I get it back? Also, the App Image Hub still produces an empty window. But the other buttons work correctly.
I followed your directions exactly, and the Flatpak Hub button disappeared from my Peppermint Hub! There is now a blank space beneath App Image Hub. How can I get it back? Also, the App Image Hub still produces an empty window. But the other buttons work correctly.
I followed your directions exactly, and the Flatpak Hub button disappeared from my Peppermint Hub! There is now a blank space beneath App Image Hub. How can I get it back?
That works! Thank you! And while we're on the subject, three similar problems with Peppermint Hub: App Image Hub and Flat hub both open empty windows. And Snap Store prompts me for my password and then does nothing. I chose Firefox as my browser. Would a different choice make these work? WAIT - I see. I had to select Snap Package Platform in the Suggested menu first. Perhaps the "Snap Store" button in the Hub could warn me to do this? However, I also selected Flatpak Package Platform in the Suggested...
That works! Thank you! And while we're on the subject, three similar problems with Peppermint Hub: App Image Hub and Flat hub both open empty windows. And Snap Store prompts me for my password and then does nothing. I chose Firefox as my browser. Would a different choice make these work?
That works! Thank you! And while we're on the subject, three similar problems: App Image Hub and Flat hub both open empty windows. And Snap Store prompts me for my password and then does nothing. I chose Firefox as my browser. Would a different choice make these work?
Here you are. Thank you in advance!
And thank you! Here is the output: Traceback (most recent call last): File "/home/edward/.local/share/pmostools/peptools/suggested.py", line 339, in <module> check_packages() File "/home/edward/.local/share/pmostools/peptools/suggested.py", line 45, in check_packages store['state'] = tk.DISABLED ^^^^^ NameError: name 'store' is not defined EDIT: after reading some other posts, I tried the same command at /etc/skel/.local/share/pmostools/peptools, and got the same error message. I don't pretend to...
And thank you! Here is the output: Traceback (most recent call last): File "/home/edward/.local/share/pmostools/peptools/suggested.py", line 339, in <module> check_packages() File "/home/edward/.local/share/pmostools/peptools/suggested.py", line 45, in check_packages store['state'] = tk.DISABLED ^^^^^ NameError: name 'store' is not defined EDIT: after reading some other posts, I tried the same command at /etc/skel/.local/share/pmostools/peptools, and got the same error message. I don't pretend to...
And thank you! Here is the output: Traceback (most recent call last): File "/home/edward/.local/share/pmostools/peptools/suggested.py", line 339, in <module> check_packages() File "/home/edward/.local/share/pmostools/peptools/suggested.py", line 45, in check_packages store['state'] = tk.DISABLED ^^^^^ NameError: name 'store' is not defined
I installed Peppermint yesterday, and am generally delighted with it. But the "Suggested" menu has stopped opening from the Welcome To Peppermint menu or the Peppermint Hub. A small window opens and closes immediately. How can I reinstall this? Many thanks for any help.
I finally got around to filing a bug with LibreOffice, where it's most likely to get attention: https://bugs.documentfoundation.org/show_bug.cgi?id=158793
You are right. Libwpd contains a WP4.x parser, but it doesn't seem to handle extended characters correctly, and the file libwpd_internal.cpp has a table of WP42 extended characters, but wpd2odt and LibreOffice do not (as you say) seem to use it correctly. The table seems to be correct, but it seems that wpd2odt doesn't correctly recognize WP4.2 files - and that isn't surprising, because the only way to do so would be to scan the file for some specific codes that may not be there at all.
You are right. Libwpd contains a WP4.x parser, but it doesn't seem to handle extended characters correctly, and the file libwpd_internal.cpp has a table of WP42 extended characters, but wpd2odt and LibreOffice do not (as you say) seem to use it correctly.
Libwpd doesn't try to convert WPDOS 4.x documents, and there's almost no way for LibreOffice to recognize that a file is a WP 4.x file, becuase it won't have a file header that identifies it. The only current applications that can open these correctly is probably WordPerfect for Windows, and it will prompt you to confirm that the file is a WP 4.2 file.
This is correct now. Thank you. I think it can be applied to LibreOffice now...
I may have may things confusing; if so, I apologize. The latest commit doesn't correct line 808 of libwpd_internal.cpp. The line should read: 0x03a8, 0x03c8, 0x03a9, 0x03c9, 0x03ac, 0x03ad, 0x03ae, 0x03af, Notice that the seventh code is 0x03ae, NOT 0x03a5 as it is now. This is the only thing that needs to be changed. Thank you for this!
Thank you! One character is now incorrect, because the code before the old commit had an error that was later fixed. To clarify, the second of the three changed lines should NOT have the change from 0x03ae to 0x03a5 shown below: 0x03a8, 0x03c8, 0x03a9, 0x03c9, 0x03ac, 0x03ad, 0x03ae, 0x03af, <--CORRECT 0x03a8, 0x03c8, 0x03a9, 0x03c9, 0x03ac, 0x03ad, 0x03a5, 0x03af, <-- WRONG The other two changed lines now have the correct code. I built your latest commit under macOS and can confirm that only one...
This is now fixed. Thank you. Is there a way to close this ticket?
For what it's worth, I've posted a guide to building the libwpd/libwpg/writerperfect executables under Windows: http://www.columbia.edu/~em36/wpdos/libwpd.html Notice that the address begins with "http://" If you get a 404 error, that's because your browser changes http:// to https:// Change it back to http:// and the page will open.
Wrong colors in SVG and ODG output
Further notes: One reason to want perfectspot is that there seems to be no other open-source WPG viewer out there. Also, I wonder if it might be possible to add the actual paths for Qt4 in the CMakeLists.txt file. I've seen suggestions online that this may work, but I can't begin to guess how to do this.
Build perfect spot on macOS or Cygwin?
I've done some further testing, and the change definitely should be reverted, because it substituted the correct characters with characters that would print in an obsolete program that got it wrong. Both Corel (in current WordPerfect for Windows) and Microsoft (with its WP import filter) use the original mapping that got changed incorrectly. Here is a WordPerfect for DOS 5.1 file with the four relevant characters: https://www.dropbox.com/s/hogzhfhx4ulm8wr/GREEKWP5.WP?dl=0 Here is the same file opened...
I've done some further testing, and the change definitely should be reverted, because it substituted the correct characters with characters that would print in an obsolete program that got it wrong. Both Corel (in current WordPerfect for Windows) and Microsoft (with its WP import filter) use the original mapping that got changed incorrectly. Here is a WordPerfect for DOS 5.1 file with the four relevant characters: https://www.dropbox.com/s/hogzhfhx4ulm8wr/GREEKWP5.WP?dl=0 Here is the same file opened...
libwpg: fix configure.ac to build in Windows
I've done some further testing, and the change definitely should be reverted, because it substituted the correct characters with characters that would print in an obsolete program that got it wrong. Both Corel (in current WordPerfect for Windows) and Microsoft (with its WP import filter) use the original mapping that got changed incorrectly. Here is a WordPerfect for DOS 5.1 file with the four relevant characters: https://www.dropbox.com/s/hogzhfhx4ulm8wr/GREEKWP5.WP?dl=0 Here is the same file opened...
Update: thanks to the generous and patient help of Laurent Alonso, I was able to build WriterPerfect 0.9.6 under both MinGW and Cygwin. I needed to make three changes in the source code, and will post a patch when I've got the details correct.
I get the same error message when I try to configure in cygwin and WSL Ubuntu. Is it possible that something is wrong in the code? Has anyone built current libwpd for Windows?
Trying to build under Windows
It's easy to test which is right. Export the Greek character set from WP5 (perhaps using LibreOffice to producde the output) and see if those characters match the unicode glyphs with the same name. You'll see that the two characters I mentioned are incorrect. The report on the change was made so that output from a commercial product called Printer Polyglott looked right; it seems that Printer Polyglott had mistakes that LibreOffice and modern Linux doesn't have.
Wrong characters in WP5 Greek character set
I've put together a complicated (but I hope working) way to run vDos in OS X. It consists of an Applescript launcher that loads a Wineskin "wrapper" for vDos.exe. When you run it the first time, it will create (and requires) a folder named vDosDisk in your home folder in OS X. This folder will be drive C: when vDos opens. Drive X: in vDos will be your OS X desktop. Drive W: in vDos will be the "Windows" directory inside the Wineskin wrapper, which may or may not be useful to you. You will need to...
And ignore my last question: I forgot that I also needed to use —enable-shared=NO
And ignore my last question: I forgot that I also needed to use —enable-shared=NO On Jun 11, 2018, at 10:42 AM, alonso laurent osnola@users.sourceforge.net wrote: Hello, do you do a make clean all (or better ./autogen.sh ; ./configure; make clean all ) ? Ie. I just check and the build ends succefully on my mac ( which is also in OSX 10.13) .... [tickets:#16] Cannot build in macOS 10.13: symbols not found for arch x86_64 Status: open Milestone: untriaged Created: Mon Jun 11, 2018 12:37 AM UTC by Edward...
Hello, Thank you for this. I tried ./autogen.sh ; ./configure; make clean all - and the errors disappeared. Thank you again! But now, oddly enough I cannot seem to create a static build. I used ./configure —enable-static and ./configure —enable-static=YES, but the resulting executables in in the src/conv/ folder were all 6KB, and make install created builds that are 300-600KB, not the 1.9MB that seem to be needed for standalone executables. Am I missing something obvious? Apologies for my incompetence!...
Cannot build in macOS 10.13: symbols not found for arch x86_64
This is a forum about vDos, which handles these things differently from vDosPlus. Please ask your question in the vDosPlus forum.
The FreeDOS SORT command and Vernon Buerg's SORTF both run in vDos. They're both fairly easy to find online, e.g. http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/sort/
Create an autoexec.txt file that contains (at least) this line: %win_vdos% That runs whatever command you use as a parameter for vdos.exe. Of course you can add "cls" and "use etc" and "path" and "exit" and anything else you want in autoexec.txt (or you can include them in your batch file).
Create an autoexec.txt file that contains (at least) this line: %win_vdos% That runs whatever command you use as a parameter for vdos.exe. Of course you can add "cls" and "exit" and anything else you want in autoexec.txt.
Thanks for the kind words, glad to hear vDos is that useful to you. To the playing sound issue: You could start with what opening a sound file at the Windows command prompt brings. If that’s somehow adequate, try to run/execute the sound file from within FoxPro, don’t know if FoxPro allows to run non-executables. Otherwise use CMD/START or CMD.EXE/START.EXE (vDos latest version), or the PDF reader approach. I found to links to playing sound at the command prompt, there will certainly be more: https://www.thefreewindows.com/19584/invisible-batch-script-play-sound-file/...
Thanks for the kind words, glad to hear vDos is that useful to you. To the playing sound issue: You could start with what opening a sound file at the Windows command prompt brings. If that’s somehow adequate, try to run/execute the sound file from within FoxPro, don’t know if FoxPro allows to run non-executables. Otherwise use CMD/START or CMD.EXE/START.EXE (vDos latest version), or the PDF reader approach. I found to links to playing sound at the command promppt, ther will certainly be more: https://www.thefreewindows.com/19584/invisible-batch-script-play-sound-file/...
That is a very generous post, but all the credit for vDos belongs to Jos Schaars!
This is a printer problem . It has nothing to do with vDos. Please ask about it elsewhere.
In a previous message, you wrote that you are running Q&A under DOSBox. Files can get corrupted in various ways under DOSBox and it seems at least possible that DOSBox has something to do with your problem. This forum is concerned with vDos, not DOSBox. For all DOSBox-related questions, please try the DOSBox forum instead: https://www.vogons.org/viewforum.php?f=53 Or try running your program under vDos.
In a previous message, you wrote that you are running Q&A under DOSBox. Files can get corrupted in various ways under DOSBox and it seems likely that DOSBox has something to do with your problem. This forum is about vDos, not DOSBox. For DOSBox-related questions, please try the DOSBox forum: https://www.vogons.org/viewforum.php?f=53 Or try running your program under vDos.