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

Evgenii

Members
  • Posts

    26
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Evgenii reacted to Dan C in [AfPub] Export to PDF breaks Combining Diacritical Marks   
    The information I provided is an excerpt of a comment from our developers on the original bug report for the issue that has been logged against all 3 of your threads here on the forums - which can be seen in the 'Tags' section of each thread (AFD-1907).
    Unfortunately I'm not personally familiar with font tables and therefore I can't provide much further clarification surrounding this - though my apologies if this does not align specifically with the issue you've reported above.
    There are many similar reports of Hindi, Bengali, Thai & Myanmar diacritics failing to export to PDF from Affinity logged in the same development report as your report (AFD-1907) and it's possible the comment regarding Morx tables was specific to one of these reports, rather than a generic comment as to the cause of the issue across multiple fonts/languages.
    The issue is still logged with our developers and is a known issue for the diacritics shown in your thread, as well as for multiple other fonts/languages - the exact reason for which may differ slightly between document/font/language, but essentially remains a known, unsupported feature of the apps when exporting to PDF at this time.
  2. Like
    Evgenii reacted to Dan C in [AfPub] Export to PDF breaks Combining Diacritical Marks   
    Hi @Evgenii,
    Thanks for your report - I can confirm this issue is still logged with our development team at this time.
    The officially logged bug is due to Affinity not supporting 'morx' tables with fonts, which causes this issue when exporting.
    Our dev team have confirmed that adding support for these font tables are unfortunately no small task and although this is something we do hope to implement in the future, we don't currently have any timescale for this - as our team are focusing on other features at this time.
    I have updated the relevant bug report with our dev team for you now. I hope this clears things up!
  3. Like
    Evgenii reacted to MikeTO in Vertical position of sidenotes   
    FYI
     
     
  4. Like
    Evgenii reacted to PaoloT in Publisher 2 and ICML files   
    I found a way to convert ICML files generated by Pandoc to IDML files that Publisher can read. This is tried on very basic files, so I don't know how it works on real, long and complex files.
    First of all, I've exported from InDesign CS6 a very basic IDML template. It contains nothing but the default settings generated by InDesign on a new document.
    IDML-Template.idml.zip
    Then, from Scrivener I've compiled a simple Pandoc-flavored markdown file, containing a text that I want to load in Publisher.
    Scrivener-source-in-Pandoc.md.zip
    I then used Pandoc to convert it to an ICML file. I used the simplest of the commands, generating the headless output in the Mac Terminal:
    pandoc -f markdown -t icml input_file.md With BBEdit, I opened a copy of the IDML-Template.idml file, and replaced the text included inside the ParagraphStyleRange tags:

    It is very important that the "Story Self=" tag matches the name of the current Story, as shown in the list of XML files inside the IDML package.
    The resulting IDML file opens fine in Publisher (V1):

    It would be great if Publisher could at least do the ICML Story replacement in an IDML template, and import it as an IDML file. Even better, it would be if it could even trigger Pandoc when importing a Markdown file, if installed on the system. It seems to be a very easy filter to program.
    Paolo
     
  5. Like
    Evgenii reacted to PaoloT in Publisher 2 and ICML files   
    Hi,
    After the new version of Pandoc (v3.0) has been released, I have to reiterate a request for ICML import to Publisher. Pandoc v3 includes an improved ICML converter.
    This converter would make going from (nearly) any markup file format to Publisher with no effort. If the source file contains text layout instructions (as you can do with Pandoc markdown, HTML, LaTeX, or Scrivener) Publisher could rebuild the layout faithfully.
    ICML is a subset of the IDML file format that Publisher can already import. It is just one of the "Story" XML files inside the IDML package. Unfortunately, there is no way that I could find to convert an ICML file into an IDML one, so at the moment Publisher can't take advantage of this Pandoc converter.
    HTML is universally used for the web, webhelp and ebooks. Pandoc and LaTeX are in strong use in the technical industry and in the academia. Such a converter would allow Publisher to be the final tool to generate PDF files from internal or end-user documentation, research materials, or web sites.
    Paolo
     
  6. Like
    Evgenii reacted to BES in add some Interactive functions   
    Add interactive functions not just adding hyperlink, basic Indesign like features such as action buttons, click, mouse rollover for, pop-ups, while we click some content it gets zoom,.
    This will be very useful to create interactive PDF export,.
  7. Like
    Evgenii reacted to PaoloT in Publisher and ICML files   
    Hi,
    Pandoc is a powerful tool for interchanging files in markdown-based formats. Among the supported formats is ICML, but not IDML.
    This might have some sense, since this is the Adobe InCopy format, and may be very useful for collaborators to publications centered in an InDesign project.
    The ICML schema should be nearly identical to IDML. I would be very happy if Publisher could read it. In particular, because it is easy to export a Scrivener project to ICML though Pandoc.
    Paolo
     
  8. Like
    Evgenii reacted to lacerto in Marks positioning in exported pdf   
    (...)
  9. Like
    Evgenii got a reaction from lacerto in Marks positioning in exported pdf   
    Yes, exactly
    I didn't create the features in FontForge, I wrote them in seperate files, that I attached above, according to specifications and imported in FF. If I export these features from FF, the syntax I believe will be different.
    But I feel like the topic is deteriorating: the problem was with the Publisher render differing from exported pdf. 
    Here's a minimalistic example font I have used above, stripped off all unnecessary features which might be causing you problems in different software: it has only two glyphs defined - a for 'a' and b for 'dieresis mark', as well as mark table to place it above.
    vertical_test.ttf
×
×
  • 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.