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

HANDJOJO

Members
  • Posts

    192
  • Joined

  • Last visited

Posts posted by HANDJOJO

  1. 2 hours ago, loukash said:

    Hm.
    Your printer seems to be an inkjet, right?
    You are using spot colors in a CMYK document.
    Also, if you apply layer effects to an object, its colors will be converted to CMYK.
    So, your PDF contains 3 spot color plates, plus some CMYK parts. That's likely what "confuses" your printer, as it usually expects RGB data.

    From what I've read here on the forums, Affinity apps are sending RGB data to printer, that's why direct printing from Publisher will likely look good.
    But I haven't tested that myself yet because it's not needed for my workflow. I actually have a CMYK laser printer, so it could be that my experience will be exactly the opposite: direct output from Affinity will be off while printing the PDF will look correct.

    Yes you right, my printer is the Inkjet with separately ink tank Color CMYK, so how to solve it, please advise.

    Thanks & B/regards,

  2. 20 hours ago, loukash said:

    Which preset?
    Please upload your .afpub document, too.

    Sory late reply your request, the preset when export to PDF is "PDF Pres Ready", only add for the bleed, crop marks.

    Herewith I attached the .afpub document along with the PDF which the printout came from.

    Awaiting advice to solve it.

    Report artefac.afpub The source PDF file have the artefact.pdf

  3. Dear all,

    Can anyone advise me how to solve a printout look artefact from PDF was created by the Publisher through Export as PDF as per sample screen shot below, however when direct print the spread everything normal didn't artefact, 

    Awaiting the advice.

    Thanks & B/regards,

    *Printout from PDF was created by Publisher through menu Export as PDF have the artefact

    Output_Printout_with_Artefact.jpg

  4. On 3/20/2021 at 1:44 AM, CrimsonEyes said:

    Hello,

    please note that every time i download the free assets like fog and rain on affinity publisher. the software freeze and doesn't respond anymore.

    please can you help me to solve this problem?

    thanks in advance

    Please try the Betta Version of Publisher there could be fix it, you can free download it if you have the Affinity Account.

  5. On 3/14/2021 at 9:45 PM, kaylon said:

    Latest 1.9.1.979

    Opens and works fine Until I select 'Print' Then it blue screens my PC and re-starts it. This happens in ALL affinity apps. But all my other apps etc are fine and work as expected.

     

     

    This was caused of the bug in Windows update KB5000802, we can only waiting from Microsoft to release the patch to solve this issue.

  6. 5 hours ago, LibreTraining said:

    The first screenshot below is your font opened in FontCreator sorted by Code-point and with the captions set to Code-points.
    Note the odd code points displayed for the characters.
    And on the left how it says: All Symbols  231
    Also note that on the left there are no Unicode blocks displayed.
    Next take a look at: Tools > Convert Font > Convert to Unicode Font  (which would be grayed-out if it already was a Unicode font).
    Click that and watch all the code points displayed change to the correct Unicode code points.
    It is making that change based on the glyph names.
    Also note that now the Unicode code blocks appear on the left. (see second image below)
    Most of the glyph names are OK, but I had to fix quite a few.
    Did it in FontLab as it was easier there.
    Then export as an actual Unicode TTF font.
    🙂

    Original:

    Batavia-in-FontCreator.thumb.png.c2e37cd2b6fcb08e0847efa0e6be47ff.png

    Converted to Unicode - now it should look like this:

    Batavia-in-FontCreator-converted-to-Unicode.thumb.png.4acf189d9c228fd39c6eaf6f81dbb459.png

     

    Also, your font is the same one he has.

    .

    Thanks All, awesome explanation and It was very interesting to find out and now clearly answered the cause, although it still leaves why others can read correctly on the same operating system.

     

  7. 9 minutes ago, LibreTraining said:

    Those apps may be loading the font as an old pre-Unicode font.

    I am guessing what font you actually have based on what I have seen happen with the fonts I found.

    Please provide the actual font you have installed and tested in APub.

     

    Ok, I send the APub file package through a Google Drive link below: 

    https://drive.google.com/drive/folders/1dNd8tF6aSIQ49Tx-10_fxWDztYADQpw1?usp=sharing

    *Screenshot in Affinity Publisher ver. 1.9.2.979.

    image.thumb.png.4bd5e8e8c794b2137b20f512f3be7819.png

  8. 5 hours ago, LibreTraining said:

    The font is defective.
    I found a few different versions of this font out in the ether.
    All are conversions of some old font. This appears to be pre-Unicode.
    The one you appear to have, where the font name is in all caps (BATAVIA), is defective.
    The characters/glyphs in the font are all assigned Unicode code points up in the PUA (Private Use Area).
    Since none of the characters are assigned to the correct code points, what you are seeing is a replacement font.
    APub sees that all the characters you typed do not appear in the font, and does replacements for the missing characters.

    I did find a couple versions of the font which do appear to be usable.
    So I made a few fixes and renamed them to BataviaAF. Download 7z file below.
    They appear to be working fine in APub.

    BataviaAF.thumb.png.c0eda73a62abaf95edc874a3a87846bf.png

    BataviaAF.7z 76.27 kB · 1 download

    Note: I did not test these extensively so there may be other issues with the original fonts.
    If you find something and it is an easy fix let me know and I can do an update.

    EDIT: I noticed the original broken font is a little narrower than the one above.
    So I am looking at converting it properly and adding it to the "family."

    EDIT again: OK. The original looks like it could be "Regular" and another one could be the Bold.
    I used the glyph names to apply the correct Unicode codes to make the Regular from the font you are using.
    Changed the bolder one to Bold.
    Made the wider one a SemiExpanded.
    Fixed a bunch of wrong Unicode codes in all of them.
    Keep in mind these fonts are messy old conversions that have been modified by multiple people probably.
    Someone added a bunch of characters/glyphs from another font to fill-in the blanks - those characters do not match.
    May be usable for what you are doing if all you need is basic Latin, numbers, etc.

    Thanks LibreTraining for your advise and your share the source of the font installer, however I still have a question I get the source from another program from another person who is working with Adobe InDesign as per screen shot attached, why the Batavia font can load well as well as in CorelDraw?.  🙄

    Awaiting the reply.

    Best regards & have a nice blessed Sunday.

     

    With Adobe InDesign.jpg

    With CorelDraw.jpg

  9. I repot another seems like a bug in Affinity Publisher version 1.9.1.979 that the Fonts cannot load correctly for i.e when I selected the Batavia Font in Publisher then the this font was wrong like figure of another font, as per screen shot attached. I have check with Microsoft Word type with Batavia Font and it is correct what the figure should it also when I check in the Directory of Windows Font also correct it.

    Please advise how to resolve it as I found this bug in Affinity Designer perhaps  also in Affinity Photo with the same version and also in new Betta version 1.9.2.1006

    Awaiting the advise.

    Thanks & B/regar

    *In Affinity Publisher ver. 19.1.979

    Wrong Load the Font in Publisher.jpg

    In Microsoft Word

    In Microsoft Word.jpg

    *In Windows Fonts Folder

    The List of Fonts.jpg

     

    *In Affinity Publisher version 1.9.2.1006

    Wrong Load in Publisher 1.9.2.1006.jpg

  10. 2 hours ago, Sean P said:

    Glad you've been able to resolve the artifacts. If you do report something to us please do try to attach any sample files you have that illustrate the problem as we do often require them to investigate. If you don't wish to attach them publicly that's fine, just let us know and we can give you a link to upload them privately. So its definitely worth saving a copy.

    With the last image - that is definitely a strange quirk with the Arial font - its also visible in Word!
    image.png

    Thanks Sean for your advise, yes it’s look strange quirk with Arial...

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