Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Loquos

  1. Haha! I'm sure he'd give it for free... but it's hand-coded and was built specifically to my needs. You'd have to know the coding he used (don't ask me, I don't know!) and how to change it to suit your needs. However, maybe there's a niche market for this? For a small fee, specific code to meet your specific needs? :-) If you're dead serious, I'll ask him if he's interested in a side job.
  2. I know a lot of people are frustrated with the lack of an integrated data merge feature in Affinity Publisher. I think we can all agree that while Adobe's InDesign had the feature, there was a lot of things even it could not do well at all. Fortunately, my husband knows a bit of coding. He created a little program for me that takes a spreadsheet converted to a .tsv file, which does the data merge into a plain text document for me, resulting in one file that I could simply cut and paste into the text frame in Publisher, and with one click add as many pages as was need to fit all the text. Yes, you could do this sort of data merge in Word if you owned Microsoft Office products, but there were variables in what I needed to do that even Word wouldn't have been able to handle. A few lines of code, and everything was done for me! Adobe could only make individual text frames for me, of EACH entry (there are over 200 entries), which I then had to stitch back together into one text frame. If a cell was empty, it would ignore, but if I had specified a coma between two values pre-data merge, then I'd have a lonely coma I'd have to go back and delete. Imagine sifting through over 200 multiline entries to find all these straggling lonely items! While Adobe's auto format during data merge is nice, the amount of time I took to set up some quick format keys in Affinity and format all the text created using my husband's few lines of code took me a LOT less time than the awkward process in Adobe. If Affinity could read and apply formats based on text markup, my husband's code solution would be absolutely perfect. But the lack of data merge isn't going to stop me from using Publisher or encouraging others to do so.
  3. Thanks! I was wondering if I was overlooking some settings that were overriding each other, but couldn't for the life of me figure out what was fighting with what.
  4. Uploading now. Please let me know if I'm missing an overriding setting somewhere. It seems to affect text frames as well. Some text frames with Style A won't align vertically correctly, while other text frames with the same Style A align vertically just fine. Would love to know what's going on. I'm including the whole file, which I should note was originally built in the Beta. So possibly there's some cleaning up to do that I've overlooked?
  5. The font has not been changed. It's the same as the one I was using during the beta, which took the alignment without any issue. After the full release, suddenly all of the text that has 'align center' format applied jumps to the top of the cell.
  6. The move from beta to open has been very smooth for me... aside from this one issue. Before, when I set text in a cell of a table to be Vertically Aligned Center, it was actually in the center of the cell. Now, it acts like there's 'space after' that it needs to account for. I've checked all my settings and I cannot figure out why it's doing this. I've included examples of the same cell text being aligned top, middle, and bottom. As you can see, the middle is not actually centered, but the top and bottom alignments are fine. I've even checked the text formatting of this cell and I don't see why it should be doing this weird thing with Aligned Center. Any idea what's causing this? My current workaround is manually doing this with cell inset measurements... but some of my cells have more than 1 line of text, so the adjustment has to be made row by row. :-(
  7. This. I've been struggling with copy and pasting from a Google Spreadsheet. Now that I have 50+ cells to pull from, the individual copy & paste wasn't going to cut it, so I dug around on the forums. I found that downloading the Google Spreadsheet as an XLSX file, then opening it in Libre Office (because that's what I have) and then copy & pasting from there seems to stop the aggravating "all in one cell" issue I was having with Google Spreadsheet. Though this was never a problem in ID, so I'm guessing it's an issue on the AP side?
  8. I was running into this same problem. Someone mentioned elsewhere that some apps code spreadsheets differently. So I downloaded the Google Spreadsheet as an XLSX file, then opened it with Libre Office. Only then was I able to get it to paste into individual cells, instead of everything in one cell. Libre Office is free to use. Try that to open the spreadsheet and then copy and paste. The fact that you cannot paste directly from Google Spreadsheets, when I know other apps that do not have this problem, seems to be an element that needs to be addressed on Affinity's side - and apparently specifically for Macs as well?
  9. And I wasn't even trying! (Though I was seriously concerned I was overlooking something obvious.) Good to know it's not just me. Whew!
  10. I should mention my above 'solution' isn't permanent, as the styles in the panel continue to show as the color they are in my screenshot above, and any time I lay out new text and apply one of those paragraph styles, I have to repeat the process to get it to be the right color.
  11. It appears to still be an issue. I am currently on - in which the assets panel now works again. Here's what I'm doing every time I work on this layout: I do a Save As to create the next edition of this publication. I edit the spot color, which updates all the elements on the layout - even articles already laid out with the Drop Cap applied. HOWEVER, as soon as I delete the old text in that frame, insert new text, and apply the First Paragraph style to the new text, the Drop Cap color reverts to a spot color used in the original origin file. This seems to be an issue with bullets as well, which also refer to the Drop Cap character style to pull the color from. The Article Title is the correct color, which refers directly to the spot color, and not the "drop cap" character style - so maybe the issue is having a paragraph style refer to a character style for color? But if so, why is it pulling different colors for the First Paragraph and Bullets? I've attached screen shots for reference. The only way I can get either First Paragraph or Bullets paragraph styles to become the correct color is to go into the Drop Cap character style, change the color to any other color, close the panel, then open it back up again, and change the color back to the spot color. Only then does it take the color correctly.
  12. Of course! No reason it has to be an exact copy of every other layout program! :-)
  13. Yes, but that's not what I'm doing. I'm 'saving as' a file to make the new issue, then editing the spot color (which is part of the Document swatch). Which seems to update everything to the new color just fine except for the Drop Cap style. It should update all of the styles that refer to that spot color. But it doesn't for the Drop Cap. It still picks up the old spot color, even if in the settings panel is says it is using the new one. Including screenshots here.
  14. Just an FYI, I don't know any design program that has that feature. It's a coding thing, CSS/HTML, not a design thing. Certainly not offered by InDesign. Definitely not in something more basic like Excel. You can select a column and tell it how wide to be. When you adjust other columns, it won't affect the size of the column you've specified a width for. So simply set each of those dummy columns to your preferred width, and you're good to go.
  15. No, and I could have sworn I had posted that in the features request, but I'm not easily finding it now. Definitely speak up about it! Would save me some time and headache when a client wants to make an order change and I have to do a little dance to shuffle everything back around.
  16. The lines of a table won't determine the width between your cells. You could make them 50 points thick and they would just run into and cover up the content in your cells. Consider them as decoration, not an element that adjust space between cells. If you must have cells with a fill, but you want clear space between those cells, the best way to do that is with inserting dummy cells with no fill or stroke. Your only other option would be to ditch the table entirely and grid out the whole thing, making individual boxes with text, and then adjust the spacing between them as it suits you - not as quick to go an edit should the content of your 'cells' change.
  17. Perhaps this is a user error, and not a bug, but it's driving me bonkers. Help! I have a 20-page publication for a client I handle every other month, and each month they like having a new color theme. I have always handled this by creating a global spot color, and then editing that color each month so that all colors change across the document. One edit, and everything updates! This seems to work fine with everything aside from Drop Cap styles. I want the Drop Cap to refer to the theme color. I have a special Drop Cap Character style that is linked (supposedly) to the global spot color. This Drop Cap Character style is referred to in a Paragraph Style, which I apply to the first paragraph of each article, with a Next Style of the regular non-Drop Cap text. EACH MONTH I go through the agony of having to open and edit the Drop Cap color. Otherwise, for whatever reason, when I apply the Paragraph Style, it pulls the OLD spot color from the previous issue, instead of the updated Spot Color. In fact, I have to open the Character Style, select another swatch, CLOSE the style, then OPEN IT AGAIN, and select the global spot color and close the style again for it to update correctly. Nothing else seems to work. I have paragraph rules that also refer to this spot color and update just fine. I have various graphic elements at various tints that refer to this spot color and update just fine. I even have tables that refer to this spot color and update just fine. It only seems to be Drop Cap that is affected. Please let me know if I'm doing something wrong, or if this is a bug. Thanks! (I am running the Publisher Beta, though this has been an issue for months and I simply haven't bothered to report it. I'm an a 2017 MacBook Pro running OS 10.14.3.)
  18. I have been on a Mac (at home) since childhood. My father worked as a computer IT (back when discs were the size of pizzas) for DuPont and always came home complaining about all of the problems with Microsoft, Dell, etc. So I've learned to navigate Apple-friendly software alternatives since I was about 8 years old. (I started on Graphic Converter AGES ago!) As the majority of my paid work is creating layouts and wrangling text, I would have preferred to 'story board' something of this experimental nature, before assembling. This way I can set myself a sort of guide for how many total pages I want to aim to end up with, what each chapter should contain, and what each page in a chapter should contain (more or less). I find it always easier to edit down text. I'd start laying out each chapter by blocking/framing, adding the essential images, charts, etc. And then add the primary text - if there's too much text for a particular space, I edit down OR consider adding a 2-4 pages to the chapter. For layouts and design, I prefer to plan, then do. But I recognize everyone works a bit differently. Since this is your own project, and not client work, I say do what works best for you! I agree the 'book' feature would be the best way to tackle this from a layout perspective - but as we don't know yet whether this will be included once Publisher is released from beta, at this stage I'd recommend keeping it all together. The biggest thing I've laid out so far on Publisher beta is a 20 page 'newsletter/magazine' for a client. It worked quite well (even better once they fixed the master page bug) and I'm already planning to continue with doing this project in Publisher each issue, ready to throw my cash at Affinity as soon as they release the paid version. I have one other annual client project that's 100+ pages and 8 beefy 'chapters' to wrangle, which is currently in InDesign and uses their 'book' feature. Though, the more I think of it, the only reason I made it a book in the first place was because ID was soooo clunky on my older Mac once you got past 25 pages or so that it was a total headache every time I had to open and work on that one massive file. Maybe Publisher (like Designer & Photo) will handle these same tasks smoother, and not having a 'book' feature when they release it from beta won't hinder my ability to cut the Adobe cord completely. Still would be nice, especially if a client comes back with a request to completely rearrange chapter orders!
  19. Is there any reason you're doing this directly in Publisher first? I would think basic text files (LibraOffice, Word, etc.) would be the best for writing, editing, and circulating chapters of a book. Publisher is more for final layout, I would think. Unless your book includes a lot of images you want proofed at the same time? If the are already individually saved in Publisher, as it's still in Beta, I think your best bet of merging would be to open all of the individual files, and then copy/paste into a comprehensive file? Since there is currently no 'book' feature. Then the rest (TOC and indexing) can all be done in the one file. Otherwise, if you're not in a hurry, I'd suggest waiting and hope they implement a 'book' feature so you don't have to go through that tedious work.
  20. +1 !! (I did not find this thread when I first searched for one and then ended up posting my own, but I more or less requested the same thing. A way to manage longer documents is a must!)
  21. Well then, let's make Publisher better than ID? :-D I would think, just like a search and replace, or the TOC, you could tell the program 'search for all instances of X and return the page number this entry occurs on'. You could do this for each word you need to be indexed but you wouldn't have to search for each them manually and stop to manually insert a marker each time. You'd simply input the desired word in the appropriate field when building the index, and the program inserts the page number(s). This is what I mean by 'auto index' - as opposed to the highly manually 'search, stop, insert index tag, search, stop, insert index tag' of the current workflow, which I think would grow tedious quickly. Like GREP or even Search & Replace, you could specify that words only with a specific format should be considered to tag for indexing.
  22. After poking around thoroughly in Publisher, I did not see one feature that I find incredibly handy in ID - creating 'books'. I saw another thread where someone suggested using Publisher's 'Sections' as a way to handle longer documents, though I'm not sure this is the way to go and keep the program running smoothly. ID handles books by creating a 'container' into which you can add or remove other ID files as 'sections' - allowing you to rearrange each as needed, add/remove pages inside each and automatically updating page numbers as you shift things around. You can even tell the 'book' that all section's styles should be children of 1 master style, allowing you to only have to update a style once to populate it across all sections. There is a longish publication I work on each year that I find easiest to wrangle by creating it as a 'book' instead of a 100+ page file. I'm not 100% sure I'd want to attempt this same publication in Publisher without some way to better manage these sections. I'm not saying Affinity should recreate what Adobe has done - I am suggesting they could add this feature and have it work even better than Adobe's does. :-)
  • 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.