Book a Demo

Author Topic: RTF Editor and fields  (Read 3908 times)

skiwi

  • EA Expert
  • ****
  • Posts: 2081
  • Karma: +46/-82
    • View Profile
RTF Editor and fields
« on: October 22, 2009, 07:12:53 am »
I create a field { FILENAME } in an external document and import it so the file will correctly contain the file name after generation on printing.

After importing, saving, and generating the document I see {MERGEFIELD FIELNAME }.
This doesn't do the same thing at all.

My issue is: Why are things in the document changed under my feet.

My request:
  • Minimise the changes made to documents (eg fields, styles)
  • maximise the features of RTF supported (eg style options, table otpions)
  • enhance the round trip capability and of externally generated or modified RTF documents and document artefacts and documents templates
  • fix or improve the function of numbered styles across document artefacts and model documents (ie numbering does not continue)
Orthogonality rules
Using EA16.1 (1627) on Windows 11 Enterprise/64 bit. Repositories in SQLServer2019 DB Schema 1558.
WebEA on Pro Cloud Server 4.2.64

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: RTF Editor and fields
« Reply #1 on: October 22, 2009, 11:36:12 am »
Don't forget to make it an OFFICAL request...  (using the links below)

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Graham_Moir

  • EA User
  • **
  • Posts: 749
  • Karma: +10/-15
    • View Profile
Re: RTF Editor and fields
« Reply #2 on: October 22, 2009, 09:04:55 pm »
Just a couple of things :

1) You say "fix or improve the function of numbered styles across document artefacts and model documents (ie numbering does not continue)".

This actually does work - I persevered with it with some help from Sparx and got it to work.   For me the issue is that it's not intuitive how you do this and the standard help plus the rtf white paper, while not incorrect, do not spell out the procedure you need to follow to make it happen.

2) With regard to {FILENAME} and {MERGEFIELD FILENAME} sounds as though you did this in MS-Word.   If so, I believe it was Word that changed this to include the keyword MERGEFIELD not the import process.   EA just imported the rtf you created from Word as it stood - I've had the same situation.

3) Finally, you say "maximise the features of RTF supported" which I wouldn't disagree with but I think the capabilities of the RTF generator are much improved.  What isn't so much improved is its usability - setting up and using styles just isn't intuitive for anyone who comes from using MS-Word,  but with a bit of effort it can be done, controlled and made to produce some vey nice results.

regards
G.