#1 RTF not readable by OS X TextEdit

open
nobody
None
5
2002-06-07
2002-06-07
Jim Menard
No

The RTF files generated by AurigaDoc is not readable by
the Mac OS X application TextEdit. TextEdit is the
default editor on OS X. RTF is its native format.

I look forward to using AurigaDoc.

Discussion

  • Khurshidali Shaikh

    Logged In: YES
    user_id=271087

    Hi,

    I don't have access to a Mac OS X system to test teh above
    problem. AurigaDoc uses jfor (www.jfor.org) for rtf
    generation. I have already asked about this problem to the
    jfor guys but even they don't have access to a Mac either.
    The question has been asked on the jfor list.

    In order to help me locate the problem you can carry out
    these steps
    > send me the error messages you get while rtf
    generation/viewing.

    > Confirm that AurigaDoc is configured correctly by
    converting a simple xml doc to pdf/rtf.

    > Try viewing the rtf document in a different editor/viewer
    if you have.

    > Try converting a simple xml document to rtf

    > Send me your problematic xml doc(if possible)

    > Also you could try downloading jfor and run the samples
    provided with it to see if they work properly

     
  • Jim Menard

    Jim Menard - 2002-06-10

    Logged In: YES
    user_id=106342

    > send me the error messages you get while rtf
    generation/viewing.

    When viewing, I see no error messages. TextEdit simply does
    not open the file for viewing or editing. I ran TextEdit
    from the command line, but saw no error messsages. I ran
    both "tail -f /var/log/system.log" and the Mac OS X
    "console" application, but saw no error messages printed
    there either.

    I re-generated sample.rtf from sample.xml. The generated RTF
    file has the same size as sample.rtf. When I ran the
    conversion, I saw the following error messages:

    Converting to rtf ......
    jfor V0.5.1 - see http://www.jfor.org
    Converting XSL:FO file '1023716893.xml' to RTF output
    'sample.rtf'...
    jfor.INFO:jfor V0.5.1 - setting up conversion...
    jfor.INFO:Parsing xsl:fo document...
    jfor.WARNING:addChild: container already closed
    (parent=org.jfor.jfor.rtflib.rtfdoc.RtfList
    child=org.jfor.jfor.rtflib.rtfdoc.RtfListItem)
    jfor.WARNING:addChild: container already closed
    (parent=org.jfor.jfor.rtflib.rtfdoc.RtfList
    child=org.jfor.jfor.rtflib.rtfdoc.RtfListItem)
    jfor.WARNING:addChild: container already closed
    (parent=org.jfor.jfor.rtflib.rtfdoc.RtfList
    child=org.jfor.jfor.rtflib.rtfdoc.RtfListItem)
    jfor.INFO:Writing out RTF...
    jfor.INFO:Write bookmark 'what_is_auriga_doc'.
    jfor.INFO:Write bookmark 'installation'.
    jfor.INFO:Write bookmark 'usage'.
    jfor.INFO:Write bookmark 'documentation_conventions'.
    jfor.INFO:Write bookmark 'limitations'.
    jfor.INFO:Write bookmark 'changes'.
    jfor.INFO:Write bookmark 'todolist'.
    jfor.INFO:Done converting xsl:fo to RTF.
    jfor.DEBUG:conversion took 1622 milliseconds.
    Done writing RTF output 'sample.rtf'.

    > Confirm that AurigaDoc is configured correctly by
    converting a simple xml doc to pdf/rtf.

    Generating PDF works fine. The output file has the same size
    as sample.pdf.

    > Try viewing the rtf document in a different editor/viewer
    if you have.

    I don't have any RTF readers on my Mac other than TextEdit.

    When I view sample.rtf in MS Word 97, I see a few problems.

    First, after section names like "What Is AurigaDoc" and
    "Introduction" I
    see an upper-case accented E (the accent is a circumflex).

    Also, in the "Installation" section of the sample document
    there are three numbered items. In MS Word, I see five
    items; the unnumbered lines in the sample document are
    numbered in the MS word version, like this (where "(E)" is a
    capital "E" with a circumflex accent):

    Installation(E) To install aurigadoc follow the given
    steps:-
    1 Untar the...
    2 tar -xvzf...
    3 This will create...
    4 Set the AURIGADOC_HOME...
    5 Add aurigadoc/bin...

    Finally, no page headers or footers appear anywhere.

    > Try converting a simple xml document to rtf

    Done; see the error messages above.

    > Send me your problematic xml doc(if possible)

    You already have two: sample.xml and user-guide.xml.

    > Also you could try downloading jfor and run the samples
    provided with it to see if they work properly

    I'll try that if I am able. It will require more than
    downloading JFor; I
    will also need to get Xerces.

     
  • Khurshidali Shaikh

     
  • Khurshidali Shaikh

    Logged In: YES
    user_id=271087

    Hi,

    Download the attached file (test.rtf) and try opening it in
    your viewer/editor and let me know if it works.
    Also not that headers and footer are not yer supported in rtf.

    Also let me know if you see wany strange characters in any
    of your viewer(like the E you mentioned earlier)

     
  • Jim Menard

    Jim Menard - 2002-06-11

    Logged In: YES
    user_id=106342

    The file looks OK on Windows: I see three pages. The first one displays
    the title, author, company, revision, and last modified date, and nothing
    else. The second page displays the "Test Section" section. I see no
    funny characters. However, there are no blank lines between paragraphs.
    There are carriage returns, but no space between the paragraphs. The
    third page of test.rtf is completely blank.

    Using the Mac OS X application TextEdit, I still can not read the file.

     
  • Khurshidali Shaikh

    Another Test

     
  • Khurshidali Shaikh

    Logged In: YES
    user_id=271087

    Hi,

    Try another rtf file i am attaching (test2.rtf). It is a simple file
    with no sections/bookmarks.

    The probelm here and jfor is that we not have acces to the
    kind of system you are using and so we cannot figure out
    what is wrong. You could try downloading jfor and test the
    samples and if they also dont work maybe post the problem
    on jfor list as well. The problem may be that your application
    (TextEdit) is uanble to understand some rtf construct
    generated by jfor.

    Also make a simpele rtf file like the one attached and email it
    to me. I will try comparing the document generated by both
    jfor and your app and see if anything makes sense.

     

Log in to post a comment.