Yep, can confirm now that tomorrow's MUI builds will deal with "close single tab close whole app" thing. Keep report bugs plz :)
@samo Quote:
No it's the .cd that it's not finished as not all strings still there, but my work on the .ct file was so you can include it .. but you can also include that .cd from my archive because it still indeed more completed compared to the old one ..
I probably just forgot to include .cd file which just come with sources itself, as i didn't think it was necessary to worry about catalogs at this moment. So probably your one will be again older. Let's deal with it at final line.
Yep, can confirm now that tomorrow's MUI builds will deal with "close single tab close whole app" thing. Keep report bugs plz :)
Sure, after 2 o'clock then as it's the time when the nightly will be availible )
Quote:
I probably just forgot to include .cd file which just come with sources itself, as i didn't think it was necessary to worry about catalogs at this moment. So probably your one will be again older. Let's deal with it at final line.
Naa be sure that i picked the latest, it was from the official MorphOS site, (source section --> VPDF)
Sure, after 2 o'clock then as it's the time when the nightly will be availible )
Thore rokz as usual :) Remember how it was before ? To release something we need to wait another year for some update, to fix few bugs and wait another year. Now everything fixes fast, and you have everything on next day. Just 5 years of waiting till everything with mui port start to be logical and nice :)
I trye vpdf beta3 here oin my Peg2 on some work pdf and seems that all works quite faster than on AmiPDF... Only some graphical glitches while zooming but for a beta its ok for me!
Beta 3 works very good on my X1000 but printing doesn`t work. Now i get an ouput "Failed to initialize output device" I tried it with PS printing and HP photosmart printing. At weekend i will create german.catalog and create an icon+drawericon for VPDF
I have a HPL 2300n and changing 'Output' from PS: to PRT: solved the error/warning requester,
@kas1e Translating catalog to spanish. Will send it to you ASAP. Don't know if 'VPDF_beta/conf/font/fonts.conf' is used, but maybe changing/adding to suit OS4 fonts. And is 'cachedir' path used?: <!-- Font directory list -->
I have a HPL 2300n and changing 'Output' from PS: to PRT: solved the error/warning requeste
Is it ok to use Postscript on os4 via PRT: ? Wasn't there PS: at all ? By default i didn't have PS: on os4, but maybe it some 3d party package which will make it works ?
Also, when you untick "postscript" option in vpdf's printer settngs window, you will have another way to print (at least should :) ).
Quote:
Don't know if 'VPDF_beta/conf/font/fonts.conf' is used, but maybe changing/adding to suit OS4 fonts. And is 'cachedir' path used?:
As far as i can see from the sources that not used there. I just keep it because it was in sources. I see that cache file creates in the PROGDIR:, and not in conf/font/ as it was in Odyssey for example, see poppler/poppler/GlobalParamsMorphOS.cc:
I don't have any PS: (dosdriver) assing, mount,... on my beta system niether on "plain" AmigaOS4.1 FE Update1. IIRC TurboPrint did create some sort of PS:, but not sure.
Will try without PostScript checkbox active and see what I get on my printer and post here result.
BTW do you have an uptodate .CD file? 'cos some strings (choosers on settings window) still missing.
BIG THX for all your efforts in porting VPDF, as everybody noticed seems a little more faster than AmiPDF.
I have PS: on my system as part of the turboprint package and printing to PS: with vpdf works great with my HP printer. Don't change a thing with it. :)
@kas1e wrote: So PS: it is turboprint package then, and works already. Good. Did second (non PostScript) way works for you ? ---------
The PS: device uses a gs-handler that came with the ghostscript package which was installed with the turboprint install. I don't beleive it actually uses the turboprint software itself as I don't have to run turboprint for printing to the PS: device to work. It's prints postscript output to a non-postscript printer.
I changed the vpdf print settings to non-postscript and tried to print but received the following error:
"Failed to initialize output device."
I'm using the usbprinter.device on port 0 with the 'HP_Photosmart" driver. I can print fine with this configuration from other programs. Just not from vpdf.
By the way, thanks for the great work in porting vpdf. It works quite well and is pretty fast.
One other problem I've run across that I don't see mentioned it that the table of contents "Tree" tab doesn't display any text. The tree is there and you can open and close nodes but the test labels for the nodes is not there. I can click on the top level for each node and I'm taken to the proper place in the PDF but clicking on sub items does nothing.
If the above, the workbench printing and tab closing were fixed I think all would be working properly.
So to make PS mode working, user just need to install ghostscript package (Is it on os4depot ?). So i will change nothing in that terms then. Strange through, that by default os4 install have prefs:printerPS, but didn't have PS: assign then. Why ?:)
The only problem is not PS output then, which failed to initialize device.. I do check printer's code in VPDF, and its all in the poppler_printer.cpp file, where i see that:
Btw, did you know any way of how i can use "File" printer device ? I.e. when i run prefs:printer, there i can choice "File" device, so to print or to clipboard, or to a file. But i can't make it to work even from pure notepad. What i want , is to make some settings so i will have virtual printer which will just print to file, and so i can check vpdf printing stuff without printer.
"So to make PS mode working, user just need to install ghostscript package (Is it on os4depot ?)...." It's part of TurboPrint, so if user don't have such programm PS doesn't exists.
Downloaded vpdf source code and found .CD in root. Still some string untranslated, but it's ok for now.
THX
Edited by jabirulo on 2017/1/6 9:52:11 Edited by jabirulo on 2017/1/6 10:36:13
@Jabirulo But as OS4 have GhostScript by default, as well as prefs:printerPS, maybe they have another assign for PS: instead ? I just trying to understand, why is os4 have by default ghostscript and prefs for PS printing, they didn't make PS: assign by default, and only for that assing/handler need to install whole turboprint ..
Such handler is part of TurboPrint, not AOS4 (AFAIK). AmigaOS4 has ghostscript viewer (and prints using gs) It's readme says: ... To print a file: Ghostscript:gs -dBATCH <path_to_file>tiger.ps ..
In theory there's no need for Turboprint. AmigaOS itself is able to generate Postscipt files using the right printer driver (or sometimes even the application itself - like Wordworth or VPDF ). What you get is a #?.ps file that can be sent to a PS enabled device (like jabirulo did by sending it via lpr.device to a HP PS printer) or saving it by using the "fileprint.device"...
GS is only needed if you want to *display* or manipulate that #?.ps file. As I said: in theory. I'm not at home atm, so I sadly can't do any helpful tests with my setup...
But as OS4 have GhostScript by default, as well as prefs:printerPS, maybe they have another assign for PS: instead ? I just trying to understand, why is os4 have by default ghostscript and prefs for PS printing, they didn't make PS: assign by default, and only for that assing/handler need to install whole turboprint ..
I don't have a PostScript printer but here is my understanding of how it works:
There is a PostScript printer driver in OS4. If you open Printer prefs and select "PostScript" in the Printer Driver box then PRT: is set up to send output to a PostScript printer and presumably you can use PrinterPS prefs to set PostScript defaults. I don't think the OS4 "PostScript" printer driver has anything to do with Ghostscript. It just sends the PostScript directly to a PostScript printer.
The TurboText PS: handler uses GhostScript to convert postscript to data that prints on a non-postscript printer.
I think OS4 AmiPDF and AmiGS are using Ghostscript directly to convert Postscript/PDF data for printing on a non-postscript printer. If you look at the "Print Setup" in AmiPDF you will see the same devices that are compiled into Ghostscript. There is a GHOSTSCRIPT: assignment in the startup-sequence for a reason.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
)
