Jump to content

trichens

Members
  • Content Count

    17
  • Joined

  • Last visited

Everything posted by trichens

  1. I'd suggest that you could look at using mulitple tables stacked on top of each other. I do a table that has alternating coloured lines for each row - so that's one table and I just select alternate rows and change the colour - in theory you may only need one column?? Text is in a duplicate table where the rows have a transparent background. I have a third table between the two so I can change the colour of individual cells
  2. The issue here is the differences between Unix and Windows and they way they handle C/R and L/F use. I use SublimeText ot Notepad++ for all my text editing and that does a soft-wrap at the end of the "on-screen" line - I can set this wrap at a particular character. The files it produces have no line breaks in the text unless I actually ask for one by pressing C/R ( and/or L/F). The problem you have with your vi edited files is that you are manually adding a L/F - and I'd imagine a C/R - at 70 characters - so this gets picked up as the end of a paragraph. What happens if you carry on typing without adding a line break? The only time in recent years - and that was around 20 years ago - I have come across this before the editor was breaking the lines at around 60 characters and when the resulting file was loading into other applications we got a C/R and L/F and so a new paragraph. We had to do a find and replace to get rid of then. If you are using Unix type tools can you run the text file through sed or similar to remove the extra C/R characters? There's a unix2dos tool that may produce a suitable files or you may find vi can do this with the following from the vi command line :%s/^M//g
  3. Well you can use the Ignore Spelling option which appears to add the word to the current file "dictionary" but not to the overall system dictionary. Just tried this and it will not highlight my spelling mistakes in the file where I have set them to be ignored, but when I open a new file and enter the same mispelled word it gets highlighted as being wrong. Will this achieve what you need?
  4. I'd really like to be able to link to other APub files - not merge - and although the merge process may perhaps work for a book, it doesn't work for me. I create matchday programmes for a local football club and I create each article as a separate APub file and then export as PDF. The final completed programme is assembled into a single APub file from the separate PDF files. Some pages like adverts don't have to be changed often, but others get changed for every programme I produce. For example a league table will change every issue, so I just remove the PDF for that page and drop in the new version. Page numbers exist only in the master pages for the combined file. I can then reorder pages or move things around as required, and apply or replace the required master page(s) for each section or page when I have finished. It seems to work OK; when we have matches rearranged I may have to produce three or four new issues in just ten days or so and the above allows me to do this quite quickly.
  5. Very true Walt. But having corrected everything, or accepted that the errors can be ignored, you can't continue directly on to the Export dialog. When the export process runs and it finds problems, it will offer the option to either view issues, ignore them or cancel, but having selected review you then lose the option to ignore if it's actually OK. I'd just like to review the issues, say "that's OK" and hit an Accept and Continue button on the Preflight dialog.
  6. After a search I can't see this mentioned in any other topics - sorry if it's there and I've missed. When I export to PDF I may get the Preflight dialog pop-up listing any issues. It's likely to flag up spelling mistakes that aren't actually mistakes - just not in the dictionary - and also items that don't affect what's going to be output. However having checked through these and decided that they are OK, I have to close the Preflight dialog and re-export which re-does the preflight process. I can then skip viewing the Preflight dialog and continue but... Could we not have a "Accept" or "Continue" button on the Preflight dialog itself which will just proceed directly to the Export dialog if we aren't going back to make any changes? Or is this already possible and I've just not spotted it?
  7. I've been using Eagle ( eagle.cool ) recently. It handles Affinity files and shows the file previews OK. Allows me to group together all the files from anywbto Seems to support most files I use but strangely doesn't include LibreOffice files like odt format
  8. The issue I had with working that way was that it wanted to keep the overall table width the same, so when you got to the last column it would usually be too wide. If you then adjust the table to get that last column right it would change all the carefully adjusted columns to the left so as to keep the same proportions. So you then have to go back and resize them all again. And if i recall correctly going back to insert another column was a nightmare because it doesn't resize the table - it resizes all the colmuns to fit the new one in. Something to watch out for though is that if the "early" columns need to be wider than the default values you'll have to adjust the "later" columns first otherwise you'll have issues trying to change the widths. You just need to experiment a bit to find what works for your particular layout. I had two tables laid over the top of each other. The first had 17 columns and the second 34 columns underneath. They have to be the same overall width so that I can have text in the first table and the second has two coloured cells as a backgound for each of the top table so I can have two colours behind the text. Worked OK when I got the calculator out to do the design on paper before opening the software.
  9. I've used tables a lot in APub and you're right - it can be really annoying. The only way I could get tables to work was work out the dimensions of your finished table so you can create a table with the correct number of columns and the correct finished table width and then change the column widths working from left to right. The other issue I had with tables was that APub would just crash out when making changes to them Either it would close unexpectedly or just stopped responding so I had to use Task Manager to kill it off.
  10. I must confess that I noticed when working on a new publicaton that the automatic relinking isn't working now ( 1.8.3.641), but I'm also pretty sure it used to. Just tried on 1.8..2.620 and that doesn't auto relink either so I have to select each image in turn.
  11. A search in Affinity forums gave me this from 2017 Also found this issue reported on HP forums where scanners were creating files that gave this error. Opened the "broken" PDF in Foxit Reader and it reported it as being PDF 1.3 format. Saved as new file which was saved as PDF 1.5 format and this opened OK in APub The export PDF options in Apub start with version 1.4 so perhaps it won't open an earlier version? I've found a reference to the PDF library used in Affinity not supporting export of PDF 1.3 so it's reasonable to assume that the same library won't import PDF 1.3 files.
  12. I have found an issue with exporting PDF and then using these in publications. Create a new publication, place a text box ( or some items ) and export as PDF - save and close the publication. Create a second new publication. Place the exported PDF from the first file into this new file - save and close. Reopen the first publication, re-export the PDF with the same name to over-write the original PDF file. Close publication. Reopen second publication - it always crashes for me. It seems to work OK if you have the second file open when you re-export the PDF from the first file. The second file will then bring up the Resource Manager and it can be updated.
  13. I posted this on another thread for creating a new version of the PDF with the fonts saved as curves - I found this in another Affinity Forum so just passing thsi on as a possible fix. It's worked every time I've used it. First install GhostScript - current version 9.50. I made sure the Windows PATH was updated to include the install folder. Open the Windows command line and move to the correct folder where the PDF file is. Then use the following command to create a new version of the PDF: gswin64c -dNoOutputFonts -sDEVICE=pdfwrite -o "output.pdf" "input.pdf"
  14. I found a post somewhere in one of the Affinity forums that described using GhostScript to change the fonts in the PDF file to curves. It's worked every time I've used it. First install GhostScript - current version 9.50. I made sure the Windows PATH was updated to include the install folder. Open the Windows command line and move to the correct folder where the PDF file is. Then use the following command to create a new version of the PDF: gswin64c -dNoOutputFonts -sDEVICE=pdfwrite -o "output.pdf" "input.pdf"
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.