I agree the bugs are annoying, but I really do appreciate the recently added features of red underline for spelling mistakes and a history in Find/Change dialog box. These features are time savers and make FrameMaker more enjoyable to use. I also appreciate the built-in scripting language.
My only gripe is the cost of an upgrade. I don't mind paying $400 every few versions to upgrade, but $400 to upgrade a single version is too much. Regards, Shmuel Wolfson Technical Writer 052-763-7133 On 04-Apr-13 9:05 AM, VLM TechSubs wrote: > > Maxwell, > > First, I wish to express appreciation for your sharing this > information on how to get by, given the partial demolition of a > feature which, to my knowledge, has worked just fine since the release > of FrameMaker version 1 ? that?s version ONE ? OH ? EN ? EEEEE ? ONE. > > Second, and particularly given much of the discussion here lately, > that you would even THINK of putting this in a ?next release? fills me > with a sense of utter contempt and disgust. Have you not absorbed the > many, MANY comments from many, MANY people, both here and elsewhere, > complaining that releases 10 and 11 look much more like bug fix > releases then true version upgrades, and that the UI ?improvements? > dumped upon us all in version 9 are not improvements at all, in many > ways, and break down constantly? Or are those comments just not part > of ?we take your needs very seriously?? > > I?ve gotta tell ya, it would be far, far more useful to most of us, > whose needs you take SO very seriously, if you (Adobe, not you > personally) would have your development team work on NOTHING but bug > fixes for a year or more ? and I mean NOTHING but. > > I feel unhappy writing such a harsh response, but this is a bug fix, > PERIOD. And so is almost everything else discussed here these days. We > don?t need another scripting language, we already have one that works > just fine. We don?t need ?more UI improvements?, you all have > ?improved? the UI far too much, far too miserably already. We don?t > need any more features ? at least not NEARLY as much as we need the > core product to just plain WORK!!! > > After all, is not the point of FrameMaker, in significant part, to > enable us to work more efficiently and productively than all those > Word users etc? Yes? No? Well, just in case the answer is ?yes?, > here?s a news flash for you: When we have to spend countless hours > figuring out what your substitute development team has broken most > recently, improved efficiency and productivity are NOT the typical > outcomes! The same is true when we have to hire someone, not to > develop incremental functionality, but rather to develop a bug fix > that Adobe likely won?t provide, not even from here to eternity. > > We need our shortcuts back. ALL of them. We need WHATEVER UI you send > our way to work ? first time, every time, no matter what. If your > developers don?t know how to manage pods, then get rid of them and > create something simple ? that works. (These are obviously just two > examples, not a working list.) > > So ? > > in the words of Capt. Picard, ?Make it so.? Evangelize INSIDE the > company, do whatever it takes, just get it done. > > Kind regards, > > Elchanan > > FrameMaker user since a VERY long time ago in a galaxy apparently far, > far removed from anything going on at Adobe today > > *From:*framers-bounces at lists.frameusers.com > <mailto:framers-bounces at lists.frameusers.com> > [mailto:framers-bounces at lists.frameusers.com] *On Behalf Of *Maxwell > Hoffmann > *Sent:* Wednesday, April 03, 2013 4:01 PM > *To:* framers at lists.frameusers.com <mailto:framers at lists.frameusers.com> > *Subject:* RE: Zoom Level Settings in FM 11 > > Karen, > > Thank you for bringing this to our attention. We do take your needs > very seriously, and have marked this issue for resolution in either a > patch or the next release of FrameMaker. > > Although the values on line 95 of your maker.ini file will not > currently display in the zoom pop-up menu (only the first 4 values > will show), you may sequentially go through all of the listed zoom > values by holding down control while you move your mouse wheel forward > or backward. > > Summary of tools you can use: > > *EDITS TO MAKER.INI FILE:* > > You can set the available zoom levels by editing line 95 of the > maker.ini file: > > Zoom=25, 50, 80, 100, 120, 140, 150, 160, 200, 400 > > *Summary of useful keyboard shortcuts:* > > Esc z i = In one zoom setting > > Esc z o = Out one zoom setting > > Esc z p = Fit Page in window > > Esc z w = Fit window to page > > Esc z f = Fit window to text frame > > Esc zz = Zoom to 100 percent > > Please note that you can also manually enter any percentage you wish > over the value that is displayed in the zoom menu. That zoom value > will be saved with the document. > > We hope that these workarounds help you in short term while we look at > fixing this issue. This bug has been brought to the attention of Adobe > product marketing and engineering. > > * > ------------------------------------------------------------------------ > * > > *Maxwell Hoffmann*| Product Evangelist | Adobe | p. 503.336.5952 | c. > 503.805.3719 | mhoffman at adobe.com <mailto:mhoffman at adobe.com> > > /http://twitter.com/maxwellhoffmann//- > //http://www.linkedin.com/in/maxwellhoffmann////blogs.adobe.com/techcomm/// > > /Upcoming webinars //http://adobe.ly/Pbz6xI//Recorded webinars: > //http://adobe.ly/Pbdp0J/// > > // > > On 21-Feb-13 10:08 PM, Karen Robbins wrote: > > Sorry if this has been mentioned before, but I just noticed that I > cannot set custom zoom levels in FM 11. Why was the functionality of > the old dialog box (or whatever it was called) removed? And no, I > don't mean typing into the percentage/drop-down box--you know, the one > that doesn't even look like an entry field until it is rolled over or > clicked in. If I had to type the size every time I needed to change > zoom level, I'd have the slowest workflow on the planet. > > Seriously, are users expected to modify an .ini file just to set > zoom-level settings? (I understand from Shmuel's tip on Rocky Mountain > Training's blog that it's maker.ini line 95.) Most technical > writers/editors are not programmers and are neither comfortable nor > familiar with modifying application files this way. Seems dangerous > for workgroups. Isn't that what user interfaces are for? > > --Karen > > _______________________________________________ > > > Send list messages toframers at lists.frameusers.com <mailto:framers at > lists.frameusers.com>. > > To unsubscribe send a blank email to > framers-unsubscribe at lists.frameusers.com <mailto:framers-unsubscribe at > lists.frameusers.com> > or > visithttp://lists.frameusers.com/mailman/options/framers/shmuelw1%40gmail.com > > Send administrative questions tolistadmin at frameusers.com > <mailto:listadmin at frameusers.com>. Visit > http://www.frameusers.com/ for more resources and info. > > > > _______________________________________________ > > > You are currently subscribed to framers as shmuelw1 at gmail.com. > > Send list messages to framers at lists.frameusers.com. > > To unsubscribe send a blank email to > framers-unsubscribe at lists.frameusers.com > or visit > http://lists.frameusers.com/mailman/options/framers/shmuelw1%40gmail.com > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info.
