This place is where you can suggest, discuss, and vote on ideas. If you want to create an idea for an other related product choose the appropriate group on this page.

When you select to create a new idea, there are a few things you can do to ensure RWS Development and other community participants understand the idea. See here for Idea best practices.

  • Ability to use font sizes above 186 points.

    Thomas Mangan
    • Under Community Review
    • 1 Comment
    Certain documents that are delivered to shareholders by publicly traded companies continue to integrate more and more styled content. While content that used large type sizes was often static, designs are now incorporating content that needs to be edited...

  • Direct to PDF: to meet final output requirement we need to be able to select what type of PDF will be created (PDF/A, PDF/X,...)

    Bart Terryn
    • Under Community Review
    • 3 Comments
    When we need to create a PDF for final output, many of us need to target a very specific PDF output format (like PDF/X or PDF/A) in order to adhere to standards imposed by the receiving party (like a web or offset printer or website). In order to make...

  • field 'xymacro spec' in job ticket should be named 'Main macro spec'

    Bart Terryn
    • Under Community Review
    • 0 Comments
    I was training an XPP newbie this week and while explaining how and where the system tracks down a macro, it suddenly occurred to me that the ' xymacro spec ' field in the job ticket has a confusing name. In the pathfinder interface the mx macro spec...

  • need for new CALS Inter-Tgroup Rule setting

    Bart Terryn
    • Under Community Review
    • 0 Comments
    When you are using multiple Tgroup tables in order to create tables in which the number of columns (or the widths of the columns) change in the middle, you would like to the row rule and row gutter to be consistent when going from tgroup 1 to tgroup with...

  • CSS Paged Media: return to PS sequence previously in use

    Bart Terryn
    • Under Community Review
    • 3 Comments
    A bit difficult to explain this one, so stay with me... In CSS and using the Paged Media way of setting up PS/PL spec, the way to call in PS sequence is by using the 'page' property. So something like: page: standard; will call in the PS sequence called...

  • Addition of a CLS job ticket

    Thomas Mangan
    • Under Community Review
    • 0 Comments
    A need for a job ticket at the CLS level has come up. Would the following be an enhancement that SDL would consider? Store a job ticket at the CLS level. When creating a new job in a given CLS - use the CLS level job ticket only if a GRP job ticket...

  • Switch for the listgr utility to generate XML output

    Thomas Mangan
    • Under Community Review
    • 0 Comments
    Hello, I would like to request an enhancement (switch) to the listgr utility that would allow the utility to generate structured output. Parsing the ascii report that this generates can be done, it would be much more efficient if the utility had the...

  • Status Window: Change display when using CSS

    Chris Leggett
    • Under Community Review
    • 1 Comment
    Something that had not occurred to me until someone (from SDL!) mentioned it. In the item format world we have font heights such as 10q and widths as 46p etc and these then display as such in the Status Window. However when using CSS-XML we need to enter...

  • Direct PDF - add GhostScript post processing step

    Bart Terryn
    • Idea Delivered Partially
    • 7 Comments
    The new Direct PDF option is great. It allows you to create UA pdfs, create bookmarks in a much simpler way, bypasses the sometimes gigantic PS files and it is quick. However is does have a downside as well. You have no control over the created PDF. You...

  • Extend the divuse tool on Windows to include the USER and PID info

    Bart Terryn
    • Not Considering
    • 0 Comments
    We all know the problem. Somebody wants to open a divison and the system comes back with the dreaded message that the division is in use. On unix the solution is simple. You run the divuse -p tool on that division, you will find who (user) holds the lock...