Jump to content

Loquos

Members
  • Content Count

    63
  • Joined

  • Last visited

Posts posted by Loquos


  1. On 2/28/2020 at 9:23 AM, MEB said:

    Hi big smile,
    Go to System Preferences > Keyboard section, Text tab (on top), click the Spelling dropdown on the right and select the last option Set Up.... Add/tick U.S. English  and press Done. Restart Affinity Publisher. A new English option should appear in the Language dropdown now. It has no locale/region specified - i mean it appears just as English in the list - but should work correctly: it's US English (the missing locale issue was already logged).

    OMG! I should have read further. Who would have thought 'Automatic by Language' would have been set to UK English??? Restarted Publisher after updated the System preferences... and now I can find all the styles with the 'missing dictionary' error and fix them so it stops underlining all the differences in spelling between US English and UK English. Thanks so much!


  2. On 1/18/2020 at 10:11 AM, ianstudio said:

    On my Mac my 3 Preferred Languages are set as: English US, French and Italian, and my main language is set as English US.. I still get that same issue of having only English (United Kingdom) accessible for spelling in Publisher when it comes to English.

    However if I change my Region (under Language & Region) from Switzerland.. to United States, then in Publisher my choice for spelling changes from English (United Kingdom) to English (without any further mention next to it..).

    Of course I will not keep my Region set to United States as I want my temperature, units etc to match my culture.. at the Mac System level..

     

     

    Ah! This is probably my issue. I live in Brazil, but I have my language settings set to US English. All is fine on my computer, and in Affinity Publisher preferences I can select English US, but upon restart, this option doesn't show in the Text Style option. I'd really rather not change my region to US to avoid a weird bug. I too prefer my temps, units, etc. to match the culture I'm living in on my computer. 


  3. On 1/31/2020 at 4:50 PM, undercovergypsy said:

    I wonder if your husband is willing to sell it?  :)

    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.


  4. 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. :)


  5. On 7/19/2019 at 7:05 AM, Pauls said:

    Just been looking at the file and I think the baseline grid and table are interacting with each other. We have an issue logged to allow tables to ignore the baseline grid. I can see 2 workarounds

    1) Turn on the baseline grid for the table and set the spacing to zero pt, this  seems to override the document settings 

    2) Set everything else on the grid then turn it off and set the table how you want

    And yes this will have changed during the beta due to another fix

    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.


  6. On 7/16/2019 at 11:23 AM, Jon P said:

    Loquos do you mind uploading the publisher file demonstrating this here and I'll take a look.

    Thanks

    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?


  7. 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. :-(

    Screen Shot 2019-07-04 at 14.12.47.png

    Screen Shot 2019-07-04 at 14.12.41.png

    Screen Shot 2019-07-04 at 14.12.57.png

    Screen Shot 2019-07-04 at 14.14.25.png


  8. On 10/15/2018 at 12:45 PM, riball said:

    Have tried copy and paste from PP table and highlighted more than one cell in AP but data still copied to one cell.

    I have also tried it from excel and that works fine.

    PP produces a tab delimited output when data is copied from a table, please can AP be set up to recognise tab as well as comma delimited data?

    R

    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?


  9. On 9/13/2018 at 6:12 AM, cansik said:

    No it does not work on Mac OSX with Excel and Google Sheets, I tried it again right now. Or could you give me a more detailed explanation? What I want is to copy multiple cells to the table, so I don't have to copy paste every single cell into the table. 

    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?


  10. On 3/27/2019 at 10:12 AM, GabrielM said:

    Hi both,

    Sorry for the delayed reply.

    I could not reproduce this in the latest build.

    Can you please check it again and confirm if it's still an issue?

    Thanks,

    Gabe.

    It appears to still be an issue. I am currently on 1.7.0.283 - 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.

    Screen Shot 2019-03-29 at 11.05.09.png

    Screen Shot 2019-03-29 at 11.04.14.png

    Screen Shot 2019-03-29 at 11.05.01.png

    Screen Shot 2019-03-29 at 11.06.31.png


  11. On 3/14/2019 at 2:27 PM, Silly Sausage said:

    Now that I come to think that, you must be right.

    Clearly too used to play with web publishing. If I remember correctly, Word has that functionality, but that's another thing.

    Still, I still think it would be a useful feature to have - couldn't Affinity Publisher be the first designer program to have it?

    Of course! No reason it has to be an exact copy of every other layout program! :-)


  12. On 3/11/2019 at 4:40 PM, Old Bruce said:

    I am not seeing that here. I exported the Document Pallet with global colour and then made a new document imported the Text Styles and the Document Swatches palette changed the global colour and the drop caps changed.

    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.

    Screen Shot 2019-03-14 at 12.37.34.png

    Screen Shot 2019-03-14 at 12.38.04.png

    Screen Shot 2019-03-14 at 12.39.47.png


  13. I made the mistake of clicking on the minimization arrow in the Assets Panel because I didn't want to see a sub-Category. Now I cannot open any of the Asset sub-categories, and I need to access something there!

    I've tried going to Window > Studio, and removing the Window from view & re-adding. I've tried resetting the studio view. I can select nothing in the Assets panel aside from the options and the dropdown to select another category.

    I've also tried restarting my computer. I'm out of ideas on how to get these to open again. Help!

    Running Affinity Designer Beta 1.7.0.257 on MacOS 10.14.3.

    Screen Shot 2019-03-14 at 12.01.43.png


  14. On 3/12/2019 at 3:17 AM, Silly Sausage said:

    Thanks!

    What I was really looking for was (transparent) spacing between cells, but there seems to be no such functionality.

    As I need to create some tables with 20+ rows, although a bit frustrating, adding dummy cells is an OK workaround for now.

    I do, however, hope that an option to manipulate the spacing between cells will be added later on.

    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. On 2/27/2019 at 8:05 AM, ConnectCreative said:

    Thank you! Finally, is there any way to rearrange the rows easily?

    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. 8 hours ago, Silly Sausage said:

    Was just hoping there would be a way to define the lines as transparent, but that's a good workaround - thanks!

    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 1.7.0.257, 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. On 12/26/2018 at 12:14 PM, cubesquareredux said:

    You ask why I'm writing this particular book directly in Publisher. Answer: It's a bit of an experiment. The book is about 50% "primary text" and 50% images, charts, call-outs, and marginalia of various kinds. What I find is that the positioning of all these items on the page affects the text I want to write. If I were to write the text separately without thinking about what appears next to it on the page, I'd be writing a different (and inferior) book.

    I suppose I could use a separate writing tool and then assemble collages on paper to see what's what — but I stopped doing that somewhere in the '80s.

    So far, I've written only a few chapters; eventually there will be many. Each one is relatively short. While preparing each chapter, obviously I've kept to a sort of "master format" that's common to all chapters. If I have to copy/paste all files into one, or "add them up" in some other Affinity-designed way, there should not be any conflicts.

    Yes, a "book" feature would be grand. (Honestly I'm still a little shocked that it wasn't built in from Day Zero.)

    Thanks much for your comment. Additional advice would be more than welcome.

     

    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!

×
×
  • 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.