Re: [Framers] FrameMaker 2019 Issues and First Look
"This is the 1.0 release of that code. Give them six months or a year to get the bugs out and address limitations." Absolutely. However, it will then be six months or a year before I upgrade. I'm not about to give them money on faith that it might be fixed, as in its current form it's unusable for my needs. There's also the possibility that the cure could be worse than the disease. I'll adopt a "wait and see" attitude. -Dan ___ This message is from the Framers mailing list Send messages to framers@lists.frameusers.com Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to listad...@frameusers.com
Re: [Framers] FrameMaker 2019 Issues and First Look
My guess is Adobe took Windows out of the PDF-generation loop so that Microsoft updates or selecting the wrong printer driver can't break it. This is the 1.0 release of that code. Give them six months or a year to get the bugs out and address limitations. On Mon, Sep 3, 2018 at 5:03 PM, Tom Beiswenger wrote: > > I don’t know if Adobe monitors this list, but the pdf issue, for me, also > is a deal breaker. Seems absurd that they would take something that worked > and “improve “ it so well that it now is pretty much useless. > >> On Sep 2, 2018, at 6:04 PM, Harding, Dan wrote: >> >> The new PDF creation mechanism and its inflexibility is a complete > dealbreaker for me. I need to be able to easily create my PDFs in different > locations with different names on the fly. Having neither of those aspects > settable at output time nor saved on a per-file basis is utterly dain > bramaged. ___ This message is from the Framers mailing list Send messages to framers@lists.frameusers.com Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to listad...@frameusers.com
Re: [Framers] FrameMaker 2019 Issues and First Look
I don’t know if Adobe monitors this list, but the pdf issue, for me, also is a deal breaker. Seems absurd that they would take something that worked and “improve “ it so well that it now is pretty much useless. Tom Beiswenger Bucher Emhart Glass Horseheads, NY USA tom.beiswen...@emhartglass.comj > On Sep 2, 2018, at 6:04 PM, Harding, Dan wrote: > > The new PDF creation mechanism and its inflexibility is a complete dealbreaker for me. I need to be able to easily create my PDFs in different locations with different names on the fly. Having neither of those aspects settable at output time nor saved on a per-file basis is utterly dain bramaged. > > As much as I dislike the idiosyncrasies and instability of Frame 2017 over Frame 2012, I won't be proceeding with Frame 2019 until/unless the PDF functionality is fixed. > > I expect the scaling issues to be a comparatively easier fix. > > For now Frame 2019 is DOA (for me) and I'm sticking with Frame 2017. > > Dan Harding > Assistant Director, Information Technologies > > University of Illinois Tax School > College of ACES, Department of ACE > 114A Mumford Hall, MC-710 > 1301 West Gregory Drive > Urbana, IL 61801 > Phone: 217-333-0935 > Fax: 217-244-5933 > https://urldefense.proofpoint.com/v2/url?u=http-3A__TaxSchool.Illinois.edu&d=DwIGaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=zzmJd9V-AOY-pLCA-v8cPy_mRSvZCZwNZBdUabWmOfQ&m=t2LwHLnNQJ0Eo308QMQ9mt6k4hPTyD23EWOfLJ7oRUk&s=GqUGqzyGKImbAcxdsJYK0uzSiohohPxuo6lm-t6x404&e= > > -Original Message- > From: Framers On Behalf Of Oran Petersen > Sent: Wednesday, August 29, 2018 2:44 PM > To: Digest FrameMaker > Subject: [Framers] FrameMaker 2019 Issues and First Look > > TCS 2019 > I have purchased and installed this new version on two Win 10 computers, fully updated with version 1803. One is a Surface Book with a native resolution of 3000 x 2000. The other is a Surface Pro 3 with a native resolution of 2160 x 1440. Both have a 2nd monitor of 1920 x 1080. This is now a 64 bit program. > > *The initial download from Adobe failed, showing complete when in reality it did not complete, making it impossible to install. An Adobe tech did a “back door” alternate process to fix that, and was helpful with the download and install. > > Thoughts and issues so far for FrameMaker 2019 include: > The display scaling is broken. The main high-res monitor is great, with 200% text scaling on the Book and 150% on the Pro 3. But when you move the window to the 2nd monitor it does not rescale, making the text, menus, etc. huge. All other apps, including Frame 2017 work as expected. This makes Frame 2019 almost unusable on the 2nd monitor, or imagine, on any lower res monitor. 1080 is not the newest, but is not old either. It is awful at even the lowest text display setting of 100%. Frame 2017 had some display issues, but the scaling worked fine. > > The PDF engine is a complete remake. The TCS uses Acrobat 2017, the latest version. The processing no longer uses the distiller. It is all internal. Frame “Save As” PDF does not allow you to choose your file name or storage location. The location must be set first in the Publish pod and is not held on a file basis. Frame Print Setup does allow you to choose an output folder, but the Publish output setting overrides it, so I see no value there. The only purpose for the distiller now seems to be to process postscript files to a PDF. Making a PDF in Word, Excel, etc. does allow choices for name, location, etc. > > You must set the Win 10 file associations to use Acrobat 2017 as a default for the PDF extension. If you don’t, you get nothing; no file, no error message. This may be the issue for Susan Corcoran on her Thursday post of blank PDF. > > So, overall, settings and management and creation of PDF with Frame 2019 needs work. Lots of it. Very confusing and convoluted with lots of broken code and different places to set things, some of which do not work. They did not get the interface between PDF in and out of Frame correct. Settings often do not “take” because they are stepped on by the Publish function. > > The color management is now totally automatic. There is no choice of RGB or CMYK anywhere. Evidently the new engine determines the color model for each graphic and uses it for processing. This is an improvement if it works. This was another of Susan's issues. > > So the fixes needed include: > *Display scaling across monitors with different resolution. (High Priority) *Save As PDF needs to work as it did in Frame 2017. Publish functions should be an alternative, not a requirement. The Frame settings should have priority and not default to the Publish Pod settings. > > As a workaround right now, most of us will probably use the Publish pod for everything. A real pain. > -Choose the Source Docu
Re: [Framers] FrameMaker 2019 Issues and First Look
The new PDF creation mechanism and its inflexibility is a complete dealbreaker for me. I need to be able to easily create my PDFs in different locations with different names on the fly. Having neither of those aspects settable at output time nor saved on a per-file basis is utterly dain bramaged. As much as I dislike the idiosyncrasies and instability of Frame 2017 over Frame 2012, I won't be proceeding with Frame 2019 until/unless the PDF functionality is fixed. I expect the scaling issues to be a comparatively easier fix. For now Frame 2019 is DOA (for me) and I'm sticking with Frame 2017. Dan Harding Assistant Director, Information Technologies University of Illinois Tax School College of ACES, Department of ACE 114A Mumford Hall, MC-710 1301 West Gregory Drive Urbana, IL 61801 Phone: 217-333-0935 Fax: 217-244-5933 TaxSchool.Illinois.edu -Original Message- From: Framers On Behalf Of Oran Petersen Sent: Wednesday, August 29, 2018 2:44 PM To: Digest FrameMaker Subject: [Framers] FrameMaker 2019 Issues and First Look TCS 2019 I have purchased and installed this new version on two Win 10 computers, fully updated with version 1803. One is a Surface Book with a native resolution of 3000 x 2000. The other is a Surface Pro 3 with a native resolution of 2160 x 1440. Both have a 2nd monitor of 1920 x 1080. This is now a 64 bit program. *The initial download from Adobe failed, showing complete when in reality it did not complete, making it impossible to install. An Adobe tech did a “back door” alternate process to fix that, and was helpful with the download and install. Thoughts and issues so far for FrameMaker 2019 include: The display scaling is broken. The main high-res monitor is great, with 200% text scaling on the Book and 150% on the Pro 3. But when you move the window to the 2nd monitor it does not rescale, making the text, menus, etc. huge. All other apps, including Frame 2017 work as expected. This makes Frame 2019 almost unusable on the 2nd monitor, or imagine, on any lower res monitor. 1080 is not the newest, but is not old either. It is awful at even the lowest text display setting of 100%. Frame 2017 had some display issues, but the scaling worked fine. The PDF engine is a complete remake. The TCS uses Acrobat 2017, the latest version. The processing no longer uses the distiller. It is all internal. Frame “Save As” PDF does not allow you to choose your file name or storage location. The location must be set first in the Publish pod and is not held on a file basis. Frame Print Setup does allow you to choose an output folder, but the Publish output setting overrides it, so I see no value there. The only purpose for the distiller now seems to be to process postscript files to a PDF. Making a PDF in Word, Excel, etc. does allow choices for name, location, etc. You must set the Win 10 file associations to use Acrobat 2017 as a default for the PDF extension. If you don’t, you get nothing; no file, no error message. This may be the issue for Susan Corcoran on her Thursday post of blank PDF. So, overall, settings and management and creation of PDF with Frame 2019 needs work. Lots of it. Very confusing and convoluted with lots of broken code and different places to set things, some of which do not work. They did not get the interface between PDF in and out of Frame correct. Settings often do not “take” because they are stepped on by the Publish function. The color management is now totally automatic. There is no choice of RGB or CMYK anywhere. Evidently the new engine determines the color model for each graphic and uses it for processing. This is an improvement if it works. This was another of Susan's issues. So the fixes needed include: *Display scaling across monitors with different resolution. (High Priority) *Save As PDF needs to work as it did in Frame 2017. Publish functions should be an alternative, not a requirement. The Frame settings should have priority and not default to the Publish Pod settings. As a workaround right now, most of us will probably use the Publish pod for everything. A real pain. -Choose the Source Document -Choose the output type (PDF) -Create or Choose a settings file that is what you want -Choose an Output Folder -Hit the “Generate selected Output” Icon in the pod -Hit the “View Output” Icon as desired. Wow. This is an improvement? Before I could set up the PDF in Frame once for a file and it would work for that file every time, and I could choose a file name and location if desired. The default file name and folder was always the Frame name and Frame storage location. This was much better. The above is a quick overview of a quick look at TCS 2019. There may be settings and methods to fix some of this that I have not learned yet. Your input is appreciated. ___ This message is from the Framers mailing list Send messages to framers@lists.frameuser
Re: [Framers] FrameMaker 2019 Issues and First Look
In answer to Caroline's question below: Ever since day-one the rule has been that you should have only one version of Acrobat on your machine. When I was working for a large company managing this stuff, one of my biggest issues was those who intentionally or accidently loaded two version on their machine, which usually destroyed the ability to successfully create a PDF that worked correctly. Even Reader and full Acrobat on one machine could cause issues. I would have to uninstall all of them and re-install the correct one. For the later versions, Adobe installation now removes other versions for you. So my 2 machines now have only Acrobat 2017, which is the version that comes with TCS 2019. There is now no sign of DC or earlier versions on my machines. 2017 should convert PF to Word very nicely, better than earlier versions, so should not be an issue for you. The install added an ACROBAT menu item to Word and other Office 365 products, which work well. I have also printed to PDF from older applications with no issues so far. None of them use or need the distiller. As I stated, earlier, the distiller seems needed only to convert postscript (ps) files. I surmise that it is best to install Acrobat last so that it can set up the other apps for you. Oran Petersen --- From: Caroline Tabach To: "An email list for people using Adobe FrameMaker software." Subject: Re: [Framers] FrameMaker 2019 Issues and First Look Message-ID: Content-Type: text/plain; charset="UTF-8" Question. If Acrobat DC is installed on the computer, how do they influence each other. I use it to fine tune files created in Word. To export from PDF to Word. Is there an order of installation for these? Caroline Tabach ?? ??? ??, 29 ? 2018, 22:44, ??? Oran Petersen ?< orand...@comcast.net>: ___ This message is from the Framers mailing list Send messages to framers@lists.frameusers.com Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to listad...@frameusers.com
Re: [Framers] FrameMaker 2019 Issues and First Look
Question. If Acrobat DC is installed on the computer, how do they influence each other. I use it to fine tune files created in Word. To export from PDF to Word. Is there an order of installation for these? Caroline Tabach בתאריך יום ד׳, 29 באוג׳ 2018, 22:44, מאת Oran Petersen < orand...@comcast.net>: > TCS 2019 > I have purchased and installed this new version on two Win 10 computers, > fully updated with version 1803. One is a Surface Book with a native > resolution of 3000 x 2000. The other is a Surface Pro 3 with a native > resolution of 2160 x 1440. Both have a 2nd monitor of 1920 x 1080. This is > now a 64 bit program. > > *The initial download from Adobe failed, showing complete when in reality > it did not complete, making it impossible to install. An Adobe tech did a > “back door” alternate process to fix that, and was helpful with the > download and install. > > Thoughts and issues so far for FrameMaker 2019 include: > The display scaling is broken. The main high-res monitor is great, with > 200% text scaling on the Book and 150% on the Pro 3. But when you move the > window to the 2nd monitor it does not rescale, making the text, menus, etc. > huge. All other apps, including Frame 2017 work as expected. This makes > Frame 2019 almost unusable on the 2nd monitor, or imagine, on any lower res > monitor. 1080 is not the newest, but is not old either. It is awful at even > the lowest text display setting of 100%. Frame 2017 had some display > issues, but the scaling worked fine. > > The PDF engine is a complete remake. The TCS uses Acrobat 2017, the latest > version. The processing no longer uses the distiller. It is all internal. > Frame “Save As” PDF does not allow you to choose your file name or storage > location. The location must be set first in the Publish pod and is not held > on a file basis. Frame Print Setup does allow you to choose an output > folder, but the Publish output setting overrides it, so I see no value > there. The only purpose for the distiller now seems to be to process > postscript files to a PDF. Making a PDF in Word, Excel, etc. does allow > choices for name, location, etc. > > You must set the Win 10 file associations to use Acrobat 2017 as a default > for the PDF extension. If you don’t, you get nothing; no file, no error > message. This may be the issue for Susan Corcoran on her Thursday post of > blank PDF. > > So, overall, settings and management and creation of PDF with Frame 2019 > needs work. Lots of it. Very confusing and convoluted with lots of broken > code and different places to set things, some of which do not work. They > did not get the interface between PDF in and out of Frame correct. Settings > often do not “take” because they are stepped on by the Publish function. > > The color management is now totally automatic. There is no choice of RGB > or CMYK anywhere. Evidently the new engine determines the color model for > each graphic and uses it for processing. This is an improvement if it > works. This was another of Susan's issues. > > So the fixes needed include: > *Display scaling across monitors with different resolution. (High Priority) > *Save As PDF needs to work as it did in Frame 2017. Publish functions > should be an alternative, not a requirement. The Frame settings should have > priority and not default to the Publish Pod settings. > > As a workaround right now, most of us will probably use the Publish pod > for everything. A real pain. > -Choose the Source Document > -Choose the output type (PDF) > -Create or Choose a settings file that is what you want > -Choose an Output Folder > -Hit the “Generate selected Output” Icon in the pod > -Hit the “View Output” Icon as desired. > > Wow. This is an improvement? Before I could set up the PDF in Frame once > for a file and it would work for that file every time, and I could choose a > file name and location if desired. The default file name and folder was > always the Frame name and Frame storage location. This was much better. > > The above is a quick overview of a quick look at TCS 2019. There may be > settings and methods to fix some of this that I have not learned yet. > > Your input is appreciated. > ___ > > This message is from the Framers mailing list > > Send messages to framers@lists.frameusers.com > Visit the list's homepage at http://www.frameusers.com > Archives located at > http://www.mail-archive.com/framers%40lists.frameusers.com/ > Subscribe and unsubscribe at > http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com > Send administrative questions to listad...@frameusers.com ___ This message is from the Framers mailing list Send messages to framers@lists.frameusers.com Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-
[Framers] FrameMaker 2019 Issues and First Look
TCS 2019 I have purchased and installed this new version on two Win 10 computers, fully updated with version 1803. One is a Surface Book with a native resolution of 3000 x 2000. The other is a Surface Pro 3 with a native resolution of 2160 x 1440. Both have a 2nd monitor of 1920 x 1080. This is now a 64 bit program. *The initial download from Adobe failed, showing complete when in reality it did not complete, making it impossible to install. An Adobe tech did a “back door” alternate process to fix that, and was helpful with the download and install. Thoughts and issues so far for FrameMaker 2019 include: The display scaling is broken. The main high-res monitor is great, with 200% text scaling on the Book and 150% on the Pro 3. But when you move the window to the 2nd monitor it does not rescale, making the text, menus, etc. huge. All other apps, including Frame 2017 work as expected. This makes Frame 2019 almost unusable on the 2nd monitor, or imagine, on any lower res monitor. 1080 is not the newest, but is not old either. It is awful at even the lowest text display setting of 100%. Frame 2017 had some display issues, but the scaling worked fine. The PDF engine is a complete remake. The TCS uses Acrobat 2017, the latest version. The processing no longer uses the distiller. It is all internal. Frame “Save As” PDF does not allow you to choose your file name or storage location. The location must be set first in the Publish pod and is not held on a file basis. Frame Print Setup does allow you to choose an output folder, but the Publish output setting overrides it, so I see no value there. The only purpose for the distiller now seems to be to process postscript files to a PDF. Making a PDF in Word, Excel, etc. does allow choices for name, location, etc. You must set the Win 10 file associations to use Acrobat 2017 as a default for the PDF extension. If you don’t, you get nothing; no file, no error message. This may be the issue for Susan Corcoran on her Thursday post of blank PDF. So, overall, settings and management and creation of PDF with Frame 2019 needs work. Lots of it. Very confusing and convoluted with lots of broken code and different places to set things, some of which do not work. They did not get the interface between PDF in and out of Frame correct. Settings often do not “take” because they are stepped on by the Publish function. The color management is now totally automatic. There is no choice of RGB or CMYK anywhere. Evidently the new engine determines the color model for each graphic and uses it for processing. This is an improvement if it works. This was another of Susan's issues. So the fixes needed include: *Display scaling across monitors with different resolution. (High Priority) *Save As PDF needs to work as it did in Frame 2017. Publish functions should be an alternative, not a requirement. The Frame settings should have priority and not default to the Publish Pod settings. As a workaround right now, most of us will probably use the Publish pod for everything. A real pain. -Choose the Source Document -Choose the output type (PDF) -Create or Choose a settings file that is what you want -Choose an Output Folder -Hit the “Generate selected Output” Icon in the pod -Hit the “View Output” Icon as desired. Wow. This is an improvement? Before I could set up the PDF in Frame once for a file and it would work for that file every time, and I could choose a file name and location if desired. The default file name and folder was always the Frame name and Frame storage location. This was much better. The above is a quick overview of a quick look at TCS 2019. There may be settings and methods to fix some of this that I have not learned yet. Your input is appreciated. ___ This message is from the Framers mailing list Send messages to framers@lists.frameusers.com Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to listad...@frameusers.com
