Jump to content

Tom Blyth

Members
  • Content count

    8
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Tom Blyth reacted to Fixx in Publisher does not recognize WORD .docx files!   
    We usually want some local formatting to come through. Italics, bolds, super/subscripts etc. 
    Personally I feel importing docx is possible to do very reliably. TXT files usually have problems with encoding. And yes, all docx files need cleaning up before importing.
  2. Like
    Tom Blyth reacted to LibreTraining in Publisher does not recognize WORD .docx files!   
    Regarding use cases ...
    This is very helpful for many different uses:
    Business users compiling a monthly report from many different depts/locations Newsletters collecting articles from many different authors Books with different chapters being written and/or edited by different people Etc., etc., etc ... Word has the ability to restrict which styles may be used in a document.
    So when you have multiple contributors you set them up with a document template.
    That along with a little instruction can make it easy to import multiple Word docs with little fixing required.
    Because styles allowed in the Word doc correspond directly with the target publication (in InDesign) the text is imported with no need for any mapping of styles.
    Have not tried this yet with APub.
  3. Like
    Tom Blyth reacted to Cal in Publisher does not recognize WORD .docx files!   
    Word is the standard format for manuscript of long documents. Almost every book in the book store was written and/or edited in Word, then output with InDesign or QuarkXPress. RTF support is a lot better than nothing, but the lack of support for placing Word docs would be a dealbreaker for many folks involved in long doc production. It'd be great if APub could add this soon, along with other long doc essentials like footnotes.
  4. Like
    Tom Blyth reacted to Dave Harris in Publisher does not recognize WORD .docx files!   
    The best way is to replace the italics and bold with character styles. You should be able to do that with Find and Replace. Applying a paragraph style will leave character styles, and their formatting, alone. (Make sure you have the latest beta, because there was a bug in this area.)
    Another way is from the Text Styles panel, right-click on a style and Apply "Style" and Preserve Character Formatting. However, that will keep all character formatting, including pointsize etc.
  5. Thanks
    Tom Blyth reacted to Uncle Mez in Publisher does not recognize WORD .docx files!   
    +1 for Publisher to become able to import DOC/DOCX/RTF file content.
    It will be very useful for those who do Book Editing and Publishing using APub.
    Blessings !
  6. Like
    Tom Blyth reacted to Stevde W in Publisher does not recognize WORD .docx files!   
    I started using "Pagemaker" a lifetime ago, then moved on to InDesign, But as you rightly comment, they now want a crazy monthly subscription to place it on the latest MS platforms, so that's why I migrated to P Plus, even though I had tried it in earlier versions and did not like it, but with X9 it suits me perfectly.
  7. Like
    Tom Blyth reacted to Stevekelly in Publisher does not recognize WORD .docx files!   
    I’m a Mac user, so never used pageplus.  being doing this for over 20 years now and am fully willing to support affinity. I started off on quark, and then adobe came along and promised to provide a better cheaper solution. Which they did with indesign for a while. Now they basically steal my money on a monthly basis and provide me with  a hideous bloated, bug ridden expensive monster. Affinity can have all the input they want from me if it helps us designers out and ends the Adobe monopoly. Yes .doc import is simply a must.  I’m fully behind you Affinity!
  8. Like
    Tom Blyth reacted to Stevekelly in Publisher does not recognize WORD .docx files!   
    .doc import please. I need this app to import .doc files.I am considering a move to this platform so need to know if it will be happening. My client uses ‘word’ the most widely used word processor in the world, I’m hoping you can make this happen. 
  9. Like
    Tom Blyth reacted to Roy Stedall-Humphryes in Publisher does not recognize WORD .docx files!   
    As many others have pointed out regarding Publisher, this software needs to enable, recognize 'Microsoft Word' files when scrolling down to, 'Insert Text From File'.
  10. Like
    Tom Blyth reacted to BlessedWind in Publisher does not recognize WORD .docx files!   
    Definitely agree with other participants. Word docs without conversion must be able to be imported.
  11. Thanks
    Tom Blyth reacted to Paul Sherfield in Publisher does not recognize WORD .docx files!   
    If this software is to be used in the publishing area, it must be able to import Office docs. I know all the formatting issues, so you do have to review the import, soft returns and all, that, but that is just being professional.
  12. Like
    Tom Blyth reacted to Ben in Open PagePlus (*.ppp) files   
    How would other publishing programs make this situation any different?
     
    You may decide on another package, but you would be overlooking the core reasons we began again in engineering the Affinity suite.  We have certain features that are not found elsewhere - such as our true single file format, full-scale support on iPad and being cross platform. We also aimed to redefine some tools since we were not bound by legacy requirements.  So, we've tried to put innovation first where we could.  Something that would have been impossible if all we had done was update an old application.  If we succeed with Publisher as we have with Designer and Photo, then why would you want to look elsewhere anyway??
     
    Everyone may feel sad that the Plus range is coming to an end, but a lot of what drove that decision was beyond our control.  The fact is that the way people use computers has changed rapidly - the hardware people bought and the way they acquire software.  We had to look at emerging markets - iOS being a very big one.  Continuing with the old software model would only have gone on so long anyway - the net result would likely have still been the end of the Plus range, but without Affinity to offer an alternative future.
  13. Like
    Tom Blyth reacted to Ben in Open PagePlus (*.ppp) files   
    Speaking as the person who wrote the PSD import/export code for Affinity - I can tell you that was a MAMMOTH task, and one that will never be complete - it has already taken up a huge part of the development time over the past six years.  It is also the most contentious since it is almost impossible to do a perfect round trip import/export via a third party editable file format.  But, PSD is probably the most used third party file format for us, so made the most sense to put the effort into supporting it to the degree we have.
     
    Now, in terms of our user base of the Affinity range, the percentage of people wanting to import PagePlus files compared to other formats is probably low.  If we did write an importer, we'd open ourselves up to demands for it to be accurate to PagePlus, even though it would be impossible to do a one-to-one import of some features.  As has been said before - the Affinity code base has been written from scratch.  There is no shared code with the Plus range.  To this end, it is no different to the software being written by a completely different company.  The amount of work to support import/export of what is effectively a non-native file format is very significant.
     
    Another thing to take into account is that PagePlus is effectively becoming a legacy format.  The code was written for an OS and style of application that is becoming outdated.  It also would not have been possible to port the code to accommodate platforms such as iOS in the way that we have achieved with Affinity.  This means that in future only existing user of PagePlus will be creating content in it.  That user base will naturally shrink. It also means that the future requirement for a PP importer will become less and less.  Compare that to an importer for a third party format that is staying "current" - you can see where the effort is better spent with regard to the wider user base of Affinity.
  14. Like
    Tom Blyth reacted to Daveuk in Publisher does not recognize WORD .docx files!   
    A lot of my work involves using InDesign to typeset academic books (80,000 to 200,000 words). These are invariably created in MS Word (by international academic authors) then professionally copy-edited in MS-Word. Capturing character attributes (italic, superscript, bold etc.) from this source copy is ESSENTIAL (the idea of pasting plain text is ridiculous). In my usual workflow I already open DOCX files in Word and re-save as RTF; the DOCX format is unreliable when placing into InDesign. This is a long-winded way of saying that, for me, having only RTF as the source format for placing text is not a deal-breaker.
    The lack of footnote/endnote support unfortunately is a deal-breaker for me and the AP beta is unusable for my post important projects.
  15. Like
    Tom Blyth reacted to countrycousin in Publisher does not recognize WORD .docx files!   
    Just adding my voice to the lack of support for MS Word files in Publisher. One of the features I liked about Page Plus was the ability to drop Word files straight in and have it create new pages to catch the overflow. I always ask my clients to submit manuscripts in the default Word format. I then create the book layout, and save it as a PDF to send to the printer.
  16. Thanks
    Tom Blyth reacted to TonyB in Publisher does not recognize WORD .docx files!   
    The ability to import .docx files is on our internal roadmap. Implementing .doc files is much, much harder so we can't commit to doing that work at the moment but we will continue to track its importance.
     
  17. Like
    Tom Blyth reacted to fritz franz vogel in Publisher does not recognize WORD .docx files!   
    it's not just a bit word-files, that i like to include in APu (copy&paste by small texts may be ok). but how about long texts, 200, 400 pages  (literature, scientific work with hundreds of foot or endnotes, with complex hierarchy in titling)? it would be really nice to have an automatic import instead of clicking and binding the text boxes again and again.
  18. Like
    Tom Blyth reacted to Fixx in Publisher does not recognize WORD .docx files!   
    txt format usually get special characters all wrong when transferred to different computer. Word is much more reliable. It used to be normal to massage text in Word before importing it to layout application..
  19. Like
    Tom Blyth reacted to Seneca in Publisher does not recognize WORD .docx files!   
    Copying and pasting word files to HTML documents is a completely different kettle of fish and I agree with you on this count.
    However, working with Word files in publishing is a different beast all together.
    Trust me, I consider myself a veteran in this field and am well aware of problems working with Word. 
    But it's completely unrealistic to expect people to save Word files down to .txt only and start working from there.
  20. Like
    Tom Blyth reacted to karipu in Publisher does not recognize WORD .docx files!   
    To be able to import .docx files is essential.
  21. Like
    Tom Blyth reacted to Cineman in Publisher does not recognize WORD .docx files!   
    Plenty of professionals will count on the inclusion of a Word import feature from Day 1 as well. It's a core requirement of any page layout application as the vast majority of the business world and other sectors generate their copy in Word. This feature needs to be in the first release or many people who might otherwise adopter sooner, will wait and adopt later. Of all the basic features not yet fully finished or included, I'd probably put this at the top of the list, then for next release INDD / IDML files should be at the top of the list (unless driving adoption by InDesign users is not a goal, which it may not be for the first cycle or two).
×