Since rel. 5.4 old text layout engine is gone and workaround used in 5.3 (org.openoffice.office.common | VCL = old) to prevent use of HarfBuzz has no effect. Font based tagging by embedding "data fields" in documents to process jobs used by ActiveFax is now broken.
Thus tdf#89870 is not resolved for us. Only workaround seems to stick with rel. 5.3 or use other software with different font rendering.
Steps to Reproduce:
1. Insert tags like @F211 1234567890@ in document and format this sequence with font "ActiveFax".
2. Print document on printer "ActiveFax".
ActiveFax client dialogue pops up and asks for target (e.g. fax number, mail address, ...). Fax number 1234567890 in given example is not processed or read by the application.
ActiveFax client reads and processes tags in document in background. No user interaction is required when tagging is in correct format and syntax. Only tags formatted with font ActiveFax are processed. On the resulting fax or mail attachment these tags are blanked and not visible for the receiver.
User Profile Reset: Yes
ActFax manual is here:
Data field section is on pages 96-107.
We process several thousand documents with ActiveFax tags each year and entering the data field information manually breaks workflows. Definitely a show stopper for us.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/604.4.7 (KHTML, like Gecko) Version/11.0.2 Safari/604.4.7
What kind of font is ActiveFax? This page says it's printer internal . Does it mean only the name matters when it's processed by the machine?
Also, the manual says under "5.6.2. UNIX, Linux and other Operating Systems" that in non-Windows systems the font does not matter. What's the point of requiring it on Windows systems, I wonder.
Created attachment 139255 [details]
Screenshot of ActFax properties dialogue
The ActiveFax font is a combination of Truetype font and printer internal font. Applications normally use the Truetype font which is then mapped by the printer driver to the printer internal ActiveFax font. I have attached a screenshot of where this mapping is done in the driver.
It was deprecated at 5.3, dropped at 5.4
Also, does ActiveFax install the ActFfont to system with the client service printer installation?
Have you opened a ticket with vendor ActFax?
(In reply to V Stuart Foote from comment #4)
> Also, does ActiveFax install the ActFfont to system with the client service
> printer installation?
ActiveFax client installs and registers TrueType font in Windows font folder.
> Have you opened a ticket with vendor ActFax?
They checked this case and said it looks like LibO renders the tags formatted with the ActFax font as graphics before the ActFax printer actually kicks in. Therefore the data fields are not recognized by the driver and their contents cannot be processed.
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Bug may be closed as we cannot assume to get back the old text layout engine from release 5.2 or older.
Our workaround in case of ActFax: the target fax number or email address can be included in the filename and thus will be processed by ActFax printer in background (without user interaction).
If there are many data fields used this will break the max file name length sometime. In this case you may use an external reference file tagged by @F500 in the file name where all other data fields like fax number, subject etc. can be included.
Since no alternative solution was proposed, I'll close per previous comment.