Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

"Affinity Writer" - Writing Persona / Linked Text / Markdown Processing idea


Recommended Posts

Hey all,

Long time lurker til the last few weeks when I reinstalled the Publisher beta to check up on it - I understand that AFP is predominantly a page layout focussed system (and after reading all the ePub threads I see that's a bug-bear for many people and I suspect "Affinity Writer" might be a good direction/bridge but let's avoid that for now).

I see that we can link/embed images so we can update the visual assets independently of the layout, but I've not seen anything similar for textual assets - which when writing more book/manual type content would be rather useful.

Coming from the tech world (software developer primarily) what I'd love to see is something like the following (that may be doable with simple scripting if/when that comes available):

  1. Write my main content in a .txt file, or .md Markdown file - which is becoming a de facto markup format in the developer world
  2. Processor app/script that takes the markdown, and converts that to a AFP source - mapping the relevant heading 1/2/3, bullet point, body, code styles to AFP styles before including that in an initial text frame.
  3. Content appears in AFP rendered, with styles applied

This would allow me update the .md files independent of page layout, using an editing environment more suited to writing content, running the document thru Grammarly/ProWritingAid.

I guess this could all come under a "Writing" persona.

Is this is a crazy idea, or something worth thinking about?



Link to comment
Share on other sites

18 hours ago, Mark Derricutt said:

Hey all,

Long time lurker til the last few weeks when I reinstalled the Publisher beta to check up on it - I understand that AFP is predominantly a page layout focussed system (and after reading all the ePub threads I see that's a bug-bear for many people and I suspect "Affinity Writer" might be a good direction/bridge but let's avoid that for now).

I see that we can link/embed images so we can update the visual assets independently of the layout, but I've not seen anything similar for textual assets - which when writing more book/manual type content would be rather useful.

Coming from the tech world (software developer primarily) what I'd love to see is something like the following (that may be doable with simple scripting if/when that comes available):

  1. Write my main content in a .txt file, or .md Markdown file - which is becoming a de facto markup format in the developer world
  2. Processor app/script that takes the markdown, and converts that to a AFP source - mapping the relevant heading 1/2/3, bullet point, body, code styles to AFP styles before including that in an initial text frame.
  3. Content appears in AFP rendered, with styles applied

This would allow me update the .md files independent of page layout, using an editing environment more suited to writing content, running the document thru Grammarly/ProWritingAid.

I guess this could all come under a "Writing" persona.

Is this is a crazy idea, or something worth thinking about?



Basically I think it is a good idea to have linked text files. I leave it open what format(s) that might be. I have the feeling that markdown is a little too under complex to meet the possibilities of text styles.

I strongly believe that the Affinty Team first wants to build a solid foundation of features. After that they can add features like that on top. There are several options to handle this: a) section manager, b) linked files, c) data merge (not available yet), d) something completely different ;-)

And BTW, welcome to the forum.
d.

Affinity Designer 1 & 2   |   Affinity Photo 1 & 2   |   Affinity Publisher 1 & 2
Affinity Designer 2 for iPad   |   Affinity Photo 2 for iPad   |   Affinity Publisher 2 for iPad

Windows 10 21H2 (19044.2251) 64-bit - Core i7 - 16GB - Intel HD Graphics 4600 & NVIDIA GeForce GTX 960M
iPad pro 9.7" + Apple Pencil

Link to comment
Share on other sites

1 minute ago, dominik said:

Basically I think it is a good idea to have linked text files. I leave it open what format(s) that might be. I have the feeling that markdown is a little too under complex to meet the possibilities of text styles.

Thanks for the welcome! I definitely agree with the limitations of markdown (that lack of a proper spec, Common Mark not-withstanding) are a somewhat a blessing and a curse (I'd favour AsciiDoc there, but it also has it's own issues) - I love the control that LaTeX provides me but that's also quite....  the beast to wrangle and understand - I have a long-standing love for the DocBook XML specs as they're (largely) human readable, structured, easily created by code/tooling - and separate from formatting.

If linked text was available, and some form of API for generating AP sub-docs/structural format one could write such things fairly "easy".

Link to comment
Share on other sites

4 minutes ago, Mark Derricutt said:

I have a long-standing love for the DocBook XML specs as they're (largely) human readable, structured, easily created by code/tooling - and separate from formatting.

You are obviously very far ahead of my knowledge in this department :)

This is why I assume you can understand how interesting (but complex) this feature is to be implemented. In the long run I can imagine APub to be a 'hub' for all kinds of sources and output media. But this will take its time.

d.

Affinity Designer 1 & 2   |   Affinity Photo 1 & 2   |   Affinity Publisher 1 & 2
Affinity Designer 2 for iPad   |   Affinity Photo 2 for iPad   |   Affinity Publisher 2 for iPad

Windows 10 21H2 (19044.2251) 64-bit - Core i7 - 16GB - Intel HD Graphics 4600 & NVIDIA GeForce GTX 960M
iPad pro 9.7" + Apple Pencil

Link to comment
Share on other sites

And then along comes a goof like me who just pastes a bunch of tagged text in on top of a selection in the aforesaid Writing Persona and I get upset because my headings aren't converted.

Personally I would love a tagged text format for export, be it an existing form or new one. XML has its uses.

Also I am a huge fan of .txt as the way to go for importing text. Everyone can open a plain text file.

Mac Pro (Late 2013) Mac OS 11.7.3 
Affinity Designer 2.0.4 | Affinity Photo 2.0.4 | Affinity Publisher 2.0.4 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Link to comment
Share on other sites

24 minutes ago, Old Bruce said:

And then along comes a goof like me who just pastes a bunch of tagged text in on top of a selection in the aforesaid Writing Persona and I get upset because my headings aren't converted.

Not, that I had you (goof) in mind writing '(but complex)' ;-)

Personally I'd prefer .txt or .rtf as a starting point. At the same point I am very curious about what Serif will come up with eventually.

d.

Affinity Designer 1 & 2   |   Affinity Photo 1 & 2   |   Affinity Publisher 1 & 2
Affinity Designer 2 for iPad   |   Affinity Photo 2 for iPad   |   Affinity Publisher 2 for iPad

Windows 10 21H2 (19044.2251) 64-bit - Core i7 - 16GB - Intel HD Graphics 4600 & NVIDIA GeForce GTX 960M
iPad pro 9.7" + Apple Pencil

Link to comment
Share on other sites

Just now, dominik said:

Personally I'd prefer .txt or .rtf as a starting point. At the same point I am very curious about what Serif will come up with eventually..

.rtf would be acceptable I reckon. Using pandoc to convert N-formats into .rtf ( https://pandoc.org - which I see also supports converting to InDesign ICML XML documents - probably just Stories tho) would probably work for anything I'd want - that opens up a "Story Manager" feature.

Link to comment
Share on other sites

2 minutes ago, Mark Derricutt said:

Using pandoc to convert N-formats into .rtf 

Oh! I didn't know about pandoc. Thanks for pointing to this source.

I just can't find .rtf in their matrix?

d.

Affinity Designer 1 & 2   |   Affinity Photo 1 & 2   |   Affinity Publisher 1 & 2
Affinity Designer 2 for iPad   |   Affinity Photo 2 for iPad   |   Affinity Publisher 2 for iPad

Windows 10 21H2 (19044.2251) 64-bit - Core i7 - 16GB - Intel HD Graphics 4600 & NVIDIA GeForce GTX 960M
iPad pro 9.7" + Apple Pencil

Link to comment
Share on other sites

6 hours ago, Mark Derricutt said:

It doesn't seem to be mentioned in the matrix, but in the https://pandoc.org/MANUAL.html you'll see "-trtf" as an output format. Doesn't look like it supports it as an input format tho.

Thanks for pointing me there. I found it. An interesting project. It would be worth doing some tests with several formats here: https://pandoc.org/try/ as this live tool offers RTF output as well.

d.

Affinity Designer 1 & 2   |   Affinity Photo 1 & 2   |   Affinity Publisher 1 & 2
Affinity Designer 2 for iPad   |   Affinity Photo 2 for iPad   |   Affinity Publisher 2 for iPad

Windows 10 21H2 (19044.2251) 64-bit - Core i7 - 16GB - Intel HD Graphics 4600 & NVIDIA GeForce GTX 960M
iPad pro 9.7" + Apple Pencil

Link to comment
Share on other sites

3 hours ago, dominik said:

Thanks for pointing me there. I found it. An interesting project. It would be worth doing some tests with several formats here: https://pandoc.org/try/ as this live tool offers RTF output as well.

I did some testing with writing out .docx files and dragging them into AFP - worked well, altho pulled in the styles in the doc with some standard I guess styling.  If I changed the styles in the AFP doc to something different, deleted the text content, and dragged the file back into the first text frame - all the contents flowed along nice - but the formatted did get reset to what was in the .docx ( dragging on a .rtf just crashed AFP ).

So that's something at least.

Link to comment
Share on other sites

40 minutes ago, Mark Derricutt said:

I did some testing with writing out .docx files and dragging them into AFP - worked well, altho pulled in the styles in the doc with some standard I guess styling.  If I changed the styles in the AFP doc to something different, deleted the text content, and dragged the file back into the first text frame - all the contents flowed along nice - but the formatted did get reset to what was in the .docx ( dragging on a .rtf just crashed AFP ).

So that's something at least.

Did you try to convert to RTF? I did and the result is some code. But I did not figure out how to turn this into a RTF-file that I can import into APub.

I tried to paste code into a plain text file and saved it. Then changed the extension from txt to rtf. But this didn't work.

d.

Affinity Designer 1 & 2   |   Affinity Photo 1 & 2   |   Affinity Publisher 1 & 2
Affinity Designer 2 for iPad   |   Affinity Photo 2 for iPad   |   Affinity Publisher 2 for iPad

Windows 10 21H2 (19044.2251) 64-bit - Core i7 - 16GB - Intel HD Graphics 4600 & NVIDIA GeForce GTX 960M
iPad pro 9.7" + Apple Pencil

Link to comment
Share on other sites

52 minutes ago, dominik said:

Did you try to convert to RTF? I did and the result is some code. But I did not figure out how to turn this into a RTF-file that I can import into APub.

I tried to paste code into a plain text file and saved it. Then changed the extension from txt to rtf. But this didn't work.

d.

In your word processor (MS Word/LibreOffice Writer) choose "save as..." and then choose rtf file format.

Link to comment
Share on other sites

4 minutes ago, toutou123 said:

In your word processor (MS Word/LibreOffice Writer) choose "save as..." and then choose rtf file format.

Thanks for the idea. I think this does not work, though. If I do so it opens the file with the code just as if it were the text of the document. It does not interpret the code as RTF language...

d.

 

Affinity Designer 1 & 2   |   Affinity Photo 1 & 2   |   Affinity Publisher 1 & 2
Affinity Designer 2 for iPad   |   Affinity Photo 2 for iPad   |   Affinity Publisher 2 for iPad

Windows 10 21H2 (19044.2251) 64-bit - Core i7 - 16GB - Intel HD Graphics 4600 & NVIDIA GeForce GTX 960M
iPad pro 9.7" + Apple Pencil

Link to comment
Share on other sites

I just bought the final released version and was a bit disappointed that the tool lacks Markdown support.  Exporting a standard document file type to another does not inherently improve the workflow.  Ideally, source text documents can be created and edited edit in the MD, doc, rtf, txt formats in the tool of my choice and import to Publisher - enabling the writer to continue editing the source document for changes. 

Link to comment
Share on other sites

1 hour ago, Jimmod said:

Exporting a standard document file type to another does not inherently improve the workflow.

Unfortunately Markdown still isn't actually a standard format - there is no spec. There is CommonMark, and a handful of common spec patterns ( Github Flavoured Markdown, Multimarkdown etc. ) but would be nice to see some support, somehow.

I get that this isn't necessarily the responsibility of the page layout program, and is probably something you'd want across Designer, Photo, and Publisher - potentially as part of the "SmartLink".

I noticed that in the numbering sections for paragraphs/styles there a "reset after Stories" etc. etc. but that's pretty much the only place I've seen stories mentioned. Hopefully something soon will come out...

Link to comment
Share on other sites

  • 1 year later...

I'd also love to see an Affinity Editor that would expose minimal format to the content author; my particular interest would be in DocBook.  I use OxygenXML Author for this now, but having an Affinity application and persona that focuses on the text content would be great as would the ability for the Publisher persona to associate DocBook markup with visual layout styles.

Link to comment
Share on other sites

On 6/17/2019 at 4:49 AM, Mark Derricutt said:

Is this is a crazy idea, or something worth thinking about?



hi Mark.. we already can write complex book with Markdown -> export perfect PDF with Latex, without using big apps like Publisher

see for example my workflow: https://github.com/StefanoCecere/markdown_pandoc_book_template

 

PLAY WELL DIE HAPPY! Game Based Learning, Music, Parenting, Trascendence and 2042 Humanist Revolution - stefanocecere.com

Link to comment
Share on other sites

  • 1 month later...

Just commenting to add my support to this request - being able to draft in markdown would open up a lot of workflow possibilities for me and the teams I manage. Baseline features to make this useful to me:

  • Heading paragraph styles (#, ##, ###, etc. - as well as ---- and ==== markup for h1 and h2)
  • Bold and Italic character styles
  • Block quote paragraph style

Tables would be great but I know they're not standard across all Markdown flavors, and Affinity Publisher handles tables a little differently such that they would need special consideration.

I know there's other things that would need to be considered, but if I had those things my workflow would be improved dramatically.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.