Details

    • Type: Bug Bug
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: 0.92
    • Fix Version/s: None
    • Component/s: pdf
    • Labels:
      None
    • Environment:
      Operating System: other
      Platform: All
    • External issue ID:
      40106

      Description

      When rendering any .fo file with text in it AND using a font specified in the
      userconfig file, the PDFText class throws an exception. This happens not on a PC
      with jre 1.5 but does on Linux, running
      java version "1.4.2"
      gij (GNU libgcj) version 4.0.1 20050727 (Red Hat 4.0.1-5)
      I finally nailed it on line

      uniBytes = new String(a).getBytes("UnicodeBigUnmarked");

      It seems that particular JVM implementation does not support that character
      encoding. When I changed it to

      uniBytes = new String(a).getBytes("UTF-16BE");

      UTF-16BE being the new notation worked on PC *and* the linux box

        Activity

        Hide
        Glenn Adams added a comment -

        batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed

        Show
        Glenn Adams added a comment - batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed
        Hide
        Jeremias Maerki added a comment -
        Show
        Jeremias Maerki added a comment - Change done: http://svn.apache.org/viewvc?rev=426465&view=rev Thanks!
        Hide
        Jeremias Maerki added a comment -

        Yes, I think this is a safe change. "UnicodeBigUnmarked" is a synonym for
        "UTF-16BE". There's another reference about which encodings must be supported by
        a JVM: http://java.sun.com/j2se/1.3/docs/api/java/lang/package-summary.html#charenc

        Still, GNU Classpath would do good to add those synonyms, too.

        Show
        Jeremias Maerki added a comment - Yes, I think this is a safe change. "UnicodeBigUnmarked" is a synonym for "UTF-16BE". There's another reference about which encodings must be supported by a JVM: http://java.sun.com/j2se/1.3/docs/api/java/lang/package-summary.html#charenc Still, GNU Classpath would do good to add those synonyms, too.
        Hide
        Christian Geisert added a comment -

        Mmmh, looking at http://java.sun.com/j2se/1.3/docs/guide/intl/encoding.doc.html
        and http://java.sun.com/j2se/1.5.0/docs/guide/intl/encoding.doc.html its looks
        like a conforming JVM should support both encodings.
        UnicodeBigUnmarked is the Canonical Name for the java.lang API but if this is
        the only problem which prevents gcj from running FOP I'm ok with the change.
        Other opinions?

        Show
        Christian Geisert added a comment - Mmmh, looking at http://java.sun.com/j2se/1.3/docs/guide/intl/encoding.doc.html and http://java.sun.com/j2se/1.5.0/docs/guide/intl/encoding.doc.html its looks like a conforming JVM should support both encodings. UnicodeBigUnmarked is the Canonical Name for the java.lang API but if this is the only problem which prevents gcj from running FOP I'm ok with the change. Other opinions?

          People

          • Assignee:
            fop-dev
            Reporter:
            Jeroen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development