Skip to main content
J
JeffStevenson1-Visitor
1-Visitor
April 4, 2012
Question

Column Width Measurements

  • April 4, 2012
  • 10 replies
  • 1995 views

Hello all,


This may be a tall order, but I have a question on column width measurement in Styler 6.0.


We have a client that is upgraded from 5.3 to 6.0. All-in-all, the upgrade has had few issues. However, we have one issue where items are wrapping in tables in 6.0 where they did not in 5.3. Does anyone have a theory as to what may be causing the differences in column width?


The stylesheet uses CALS tables. The widths are relative (ie. 0.88*). I know it is a jump from 5.3 to 6.0. Has anyone else seen similar?

    10 replies

    E
    ebenton1-Visitor
    1-Visitor
    April 4, 2012
    Tableminimumrowheight, if set to a lower value in 6.0, that might cause some premature text breaking compared to 5.3. I don't know what the default was in 5.3 nor what it is in 6.0. You might check those values to see.
    J
    JeffStevenson1-VisitorAuthor
    1-Visitor
    April 4, 2012

    Hi Ed,


    I looked at that setting. My issue is width not height. Changing the height didn't have an effect.


    I'm wondering if anything changed regarding cell padding or hyphenation? As a test, I turned Word Breaking off for <entry>. This allowed the table cells that are wrapping to fit on 1 line with no problem, but cells that need to wrap are overwriting the following column.


    The space in question here is perhaps. 0.5pt. For instance, if the character string is "00" it wraps, but if it is "11" it won't. The difference is neither "00" nor "11" used to wrap.



    In Reply to Ed Benton:


    Tableminimumrowheight, if set to a lower value in 6.0, that might cause some premature text breaking compared to 5.3. I don't know what the default was in 5.3 nor what it is in 6.0. You might check those values to see.
    T
    tony.morales_ap1-Visitor
    1-Visitor
    April 4, 2012
    Prior to Arbortext 6.0, you could see how many of your floating licenses were being used (and by whom). There was an item under the Help menu that presented this information.

    Using Arbortext 6.0 floating flexera licenses, this option does not seem to be present. Is there a way to see how many of your flexera floating licenses are being used (and by whom) in Arbortext 6.0?

    Thanks,

    Tony

    --
    Tony Morales
    Information Tools Architect
    Oracle Corporation

    D
    DavidS.Taylor1-Visitor
    1-Visitor
    April 4, 2012
    Your problem may be related to the table cell margin settings.

    If you set top, bottom, right or left table cell margins in 5.3 to a non-integer value these will be invalid in 6.0. Beginning in 5.4, these values must be integer, measured in points.

    You might want to check the 5.4 release notes (for all 5.4 updates too) for any other changes that may cause problems in your 5.3 to 6.0 migration.

    David

    C
    ClayHelberg18-Opal
    18-Opal
    April 4, 2012
    Hi Tony--

    You can access this info using the Flexnet license administrator from
    the server where the Flexera License server is running. It's a web app.
    You can access it by going to the Start menu and choosing Start->All
    Programs->PTC->PTC Flexnet Admin License Server-> PTC Flexnet Admin
    License Server Web Interface. This will fire up your browser.

    From there, under Licenses, click Concurrent. It will show you the
    licenses enabled on the server, how many are in use and available, and
    for licenses that are in use, there will be a "Hosts" link you can click
    to get a list of clients that are using the licenses.

    HTH

    --Clay


    Clay Helberg
    Senior Consultant
    TerraXML

    N
    naglists1-Visitor
    1-Visitor
    April 5, 2012
    Hi Jeff,

    No direct experience, but ... hey, wait, I was going to say someone found a
    change in hyphenation from 5.3 to 5.4 caused table cells to break
    differently, but after searching, I saw it was you who told us that ... so
    maybe you forgot, maybe it's a different issue, ... not sure.



    On Wed, Apr 4, 2012 at 1:32 PM, Taylor, David S. <
    david.s.taylor@nrc-cnrc.gc.ca> wrote:

    > Your problem may be related to the table cell margin settings.****
    >
    > ** **
    >
    > If you set top, bottom, right or left table cell margins in 5.3 to a
    > non-integer value these will be invalid in 6.0. Beginning in 5.4, these
    > values must be integer, measured in points.****
    >
    > ** **
    >
    > You might want to check the 5.4 release notes (for all 5.4 updates too)
    > for any other changes that may cause problems in your 5.3 to 6.0 migration.
    > ****
    >
    > ** **
    >
    > David****
    >
    > ** **
    >
    > ** **
    >
    > *From:* Jeff Stevenson [
    M
    mbushby1-Visitor
    1-Visitor
    April 5, 2012


    Alternatively, if like me you do not have easy access to the server where the Flexera License server
    is running, you could get your system folk to run license management software that lets you check
    the license usage from any other machine. We use the light version of OpenLM. Simple and
    effective.

    -- Martin


    Martin Bushby
    Kongsberg Maritime







    J
    JeffStevenson1-VisitorAuthor
    1-Visitor
    April 5, 2012

    Hi Paul,


    Yes, it's a similar issue, but the same fix isn't working in 6.0 and we found that it didn't work in 5.4 either. This has been a longrunning project for many reasons.

    In Reply to Paul Nagai:


    Hi Jeff,

    No direct experience, but ... hey, wait, I was going to say someone found a
    change in hyphenation from 5.3 to 5.4 caused table cells to break
    differently, but after searching, I saw it was you who told us that ... so
    maybe you forgot, maybe it's a different issue, ... not sure.



    On Wed, Apr 4, 2012 at 1:32 PM, Taylor, David S. <
    @david.s.taylor@nrc-cnrc.gc.ca> wrote:

    > Your problem may be related to the table cell margin settings.****
    >
    > ** **
    >
    > If you set top, bottom, right or left table cell margins in 5.3 to a
    > non-integer value these will be invalid in 6.0. Beginning in 5.4, these
    > values must be integer, measured in points.****
    >
    > ** **
    >
    > You might want to check the 5.4 release notes (for all 5.4 updates too)
    > for any other changes that may cause problems in your 5.3 to 6.0 migration.
    > ****
    >
    > ** **
    >
    > David****
    >
    > ** **
    >
    > ** **
    >
    > *From:* Jeff Stevenson [mailto:jstevenson@gpslsolutions.com]
    > *Sent:* Wednesday, April 04, 2012 12:37 PM
    > *To:* -
    > *Subject:* [adepters] - Column Width Measurements****
    >
    > ** **
    >
    > Hello all,****
    >
    > This may be a tall order, but I have a question on column width
    > measurement in Styler 6.0.****
    >
    > We have a client that is upgraded from 5.3 to 6.0. All-in-all, the
    > upgrade has had few issues. However, we have one issue where items are
    > wrapping in tables in 6.0 where they did not in 5.3. Does anyone have a
    > theory as to what may be causing the differences in column width?****
    >
    > The stylesheet uses CALS tables. The widths are relative (ie. 0.88*). I
    > know it is a jump from 5.3 to 6.0. Has anyone else seen similar?****
    >
    > ** **
    C
    ClayHelberg18-Opal
    18-Opal
    April 5, 2012
    Hi Jeff--



    If you haven't already done so, it might be worth printing out the same
    table as published in 5.3 and 6.0, and then superimpose the pages to try
    to pin down what the exact difference is:



    * Overall table width?

    * Cell padding/margins?

    * Text size?

    * Text kerning?

    * Column widths? (If so, where is the extra space getting
    allocated that is missing from the narrowed columns?)



    --Clay





    Clay Helberg

    Senior Consultant

    TerraXML


    J
    JeffStevenson1-VisitorAuthor
    1-Visitor
    April 5, 2012

    I found the issue. In 5.4, overflowhyphen was added. Setting this to 0 took care of the issue.


    http://www.ptc.com/cs/help/arbortext_hc/ae60m030_hc/index.jspx?id=help6000&action=show


    Thanks for the help everyone!


    -Jeff

    Terms & ConditionsAccessibility statement