Jump to content
You must now use your email address to sign in [click for more info] ×

SallijaneG

Members
  • Posts

    24
  • Joined

  • Last visited

Posts posted by SallijaneG

  1. On 11/11/2022 at 12:24 PM, wonderings said:

    I can count the number of times I have used or seen variable fonts used on 1 hand. I work in print and design so get a lot of work from designer houses (not people with photoshop who call themselves designers). I think they are a great idea, but not something that drastically changes how people work in these field. Many fonts already have the gamut from light to ultra which I would think suits the vast majority of the world. Again I think variable fonts are a great idea and nice to always have options, not sure I would make such a big deal about the variable fonts not being in V2 myself. 

    It would be nice, as would color fonts, but tagged PDFs for accessibility is WAY more important.

  2. On 6/4/2020 at 2:58 PM, PaulWilliamson said:

    Hi,

    I just found out about the "place" option.  I suppose that means putting a PDF inside an existing InDesign file.  I wonder how that would work and look?

    Thanks,

    -paulw

    My assumption (and we know what happens when one assumes) is that it would look O.K., but not be editable.  Going in the other direction, InDesign to Publisher, requires the InDesign document to be output as an IDML file, and the result is good but not perfect.

  3. On 3/15/2023 at 2:49 PM, VectorCat said:

    ebooks are now a part of the publishing terrain…

    Yes, but my understanding is that requirements for e-books and printing presses are different enough that conversion is really complex.  I don’t know enough to know how much extra infrastructure is required (Is something like InDesign that does both twice the size of Publisher?  What choices in the early stages commits a project to being either paper-optimized or web-optimized?), but if it is critical for some users, they should keep pushing.  I find in my work the tagged-PDF accessibility issues more important.  Lots of users with varied needs. . . .

  4. On 3/10/2023 at 8:15 PM, HawaiiAna said:

    Same here. I would love to know too. There is a lot of talk about accessibility and some countries are implementing strict laws. It's just going to get bigger and bigger. I rarely use forums but this topic is too important and I already posted 4 comments hoping to attract Serif's attention to it. And if they are working on it why not tell everybody so we can sleep peacefully knowing the feature is coming. 

    I have a colleague who is able to do it manually with Adobe Acrobat, but we are a small grassroots group that publishes <1 document per month.  Not sure about better options for those with serious volumes, but this is a serious missing piece and should be the single item for which we all clamor.  They did listen to all the requests for footnotes, so maybe. . . . .?

  5. On 11/9/2022 at 10:58 AM, galexa said:

    I'm trying not to be shocked that they haven't included ePub and other export options in the new version. A quick search shows it being asked for in 2018 so maybe it's never going to happen. Disappointed but no need to upgrade so...

    One of the big requests was provided: footnotes!  Now we all need to keep clamoring for tagged PDF/EPUB options!

  6. On 5/13/2023 at 6:19 PM, Red Sands said:

    I have read oceans of uninformed nonsense on the subject in other threads on this forum, but we are many years into quite serious and understandable requirements and expectations for PDFs around the globe. It makes no sense to me why Serif is still in the paper world, but it makes it crystal clear to potential customers why they cannot choose Affinity. 

    Publications Office of the European Union: Accessible publishing

    Does WCAG apply to PDFs?

    Why PDF Accessibility is Important For Higher Education

    Understanding accessible PDFs (What is an accessible pdf, and why does it matter?)

    Accessible PDF Best Practices

    Not to mention equal requirements in the USA:

    Section 508 and WCAG?

    Section 508 is a law that states anytime the federal government develops, procures, maintains, or uses ICT employees and members of the public with disabilities seeking information, data or services from the Department must have the same or comparable access as those without disabilities. 

    I do a lot of hybrid publications that are printed and viewed on the Web, I had someone demonstrate what a screen reader does with a PDF and was appalled at how inaccessible they are by nature.  This is mission-critical; we need to be able to produce accessible PDFs from Publisher files, and although I am personally in an organization that has someone who can take the extra time it needs from Publisher as compared to InDesign, it will be a major stumbling block for growth.  I am an amateur; my work is for grassroots groups that cannot afford Adobe and I personally refuse to spend the extra for a subscription, but I am an exception, willing to muddle through.  Generally, this will be a deal-breaker for many.

  7. Should I post my similar problem here or as a new topic?  Early 2015 Mac, 11.7.6 Big Sur.  Publisher 2.1, a file updated from last year’s issue of the same newsletter, when printing the Zilla Slab font is partly corrupted—strange characters added over and between words; curly brackets, underscores, hyphens, ampersands, double brackets, pilcrows, ligatures (ffi, fl, etc.).  Cooper Hewitt text on same page is clean.  I copied a paragraph of Zilla Slab into Libre Office, exported it as a graphic, and the text is clean.  Attaching samples here.

    Untitled 2.png

    News&Views23Summer.pg2.pdf

    ScreenshotPDF.png

  8. 4 hours ago, MickRose said:

    Hi @SallijaneG I suspect your issue with the black background is not related to the initial post on this thread. The PDF you attached does have a clipping path which corresponds somewhat to where the black backgroud is using the Wordpress Media Library. What preset did you use to create the PDF? I made a PDF using PDF 1a 2003 and that clipping path wasn't there in the new PDF, so that might be worth trying.

    I switched to a newer PDF format and exported, no change.  I added new pages and copied the various pieces onto them, got weird results (only the header image showing up in the PDF, for instance), and this morning thought—HA!  I have 2 in the series that worked, I will just paste the text from the problem file into a clone of one of those, and it worked, exported into the Media Library with no issue.

    (BTW, I am something of an amateur; clipping path?  I’ll have to look that up.  Hmm, I did not knowingly create a clipping path—no background removal, just a few text boxes and graphics placed on a single letter-sized page; I guess it will just remain a mystery.  Thanks for your efforts.)

  9. I am putting this here because it seemed to be related; I searched “black background” to see if others had a similar problem.

    I created the file below, “2207 HOSS FactSheet” in Affinity Publisher, 1.10.5, on a Macbook Pro, Big Sur, 11.6.5, then exported as a PDF.  It looked fine, so then I uploaded it to WordPress media library, and got the file called “What the Heck?”—the text was suddenly unreadable on the black background.  I solved it by creating a white 8.5x11" rectangle, and layering it under everything else—but that is a work-around, not a solution.  I have 2 other files in the series of fact sheets, same issue, same work-around.  I just exported as a PNG, to make it easier to see the difference side by side; that file is “What 2207 HOSS FactSheet”.

    Help?

    What the Heck?.png

    2207 HOSS FactSheet.pdf

    What 2207 HOSS FactSheet.png

  10. On 7/28/2020 at 3:08 AM, firstdefence said:

    Why would you use Affinity Publisher if you can use text editors that are more suited to the type of text required for export to ePub or that export directly to ePub, Mobi, Azw etc.

    Because I am creating documents mostly for print, knew InDesign really well and transferred seamlessly to Affinity Publisher et al., and now need to make accessible documents, and just learned that EPUB is the easiest format for screen readers.  (My PDF documents are increasingly often also being posted to Web sites.)

     

    Also, Google docs eliminates all the formatting when someone opens a PDF, destroying the aesthetics on which I worked so hard—though perhaps rather than make the actual file accessible, the staff person who is doing the accessible version should go ahead and do that through Google or Libre/Open Office.

  11. On 2/4/2022 at 12:21 PM, shinebox said:

    For now, I build PDFs in Publisher and then make them accessible with Acrobat DC Pro. Not ideal to say the least, but there's no way I'll go back to Indesign and Illustrator, so it is what it is. I'll just have to eat the monthly acrobact costs.

    That is what we are doing at UUJEC; we have a subscription to Acrobat Pro through TechSoup, but it takes lots of time for our one part-time staff person to add accessibility.  Support for tagging would make this much easier!  Please, major request for version 2.0!

  12. How many records did you have?  24?  I think it copied the format of the first page to create enough boxes for each.  I cheated with mine, given that I had to get them in the mail today and still had copies to make and multiple meetings, exported the pages as JPEGs and inserted them into the Open Office template for Avery labels.  Next time, I convert the template to a PDF, import it into Publisher, and try again.

  13. I have the 3 Affinity programs (1.8.3) on Macbook Pro, Sierra 10.12.6, and have no immediate plans to upgrade my system or get a new computer.  I am was considering going to 1.8.6, checking here for system requirements, and am now concerned about the application- and file-size issues that I see in this discussion.  Can anyone tell me if I am missing a compelling reason for me to update the Affinity programs?

  14. Yes, when I create a new file and want to save it to a specific folder, unless that folder was one of the most recent I opened (Macbook Pro, Sierra, 10.12.6), I either have to go to that folder separately to open and save something, so that it becomes one of my recent places, or stash it on the desktop until I get around to dragging my documents off the desktop to their respective proper places.  An extra unnecessary step.

×
×
  • Create New...

Important Information

Terms of Use | 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.