Jump to content

Search the Community

Showing results for tags 'OpenType'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 16 results

  1. Would be nice if you could implement "palt" feature https://sparanoid.com/lab/opentype-features/#palt Additionally pwid/pkna/halt would be nice. https://sparanoid.com/lab/opentype-features/#pwid https://sparanoid.com/lab/opentype-features/#pkna https://sparanoid.com/lab/opentype-features/#halt East Asian Tetragrams (Chinese, Japanese, Korean) smpl trad tnam expt hojo nlck jp78 jp83 jp90 jp04 hngl ljmo tjmo vjmo fwid hwid halt twid qwid pwid palt pkna ruby hkna vkna Ultimately I would like you to add "Mojikumi" feature that's set of templates for kerning. https://helpx.adobe.com/indesign/using/composing-cjk-characters.html#change_mojikumi_settings
  2. I've noticed that all the Affinity applications have trouble with the Contextual Alternates feature (on by default). The 'error' occurs when the entered text has an initial capital. Specifically when the applications auto capitalise the first word. All OK in Adobe applications etc.
  3. Affinity Publisher 1.7.0.139 on Windows 7 (64bit, German) behaves as follows: Create a text with a font that supports several OpenType features like stylistic sets. The screenshot was done with 'TheSans E4s' by known font designer Lucas de Groot. With no OpenType feature used, the text always behaves properly. With certain OpenType features enabled, the metrics of corresponding characters become garbled, so that the resulting text is sometimes unusable. For reference, the screenshot shows shaded fields and blue text frames. Here some remarks concerning the image: The 1st and 2nd line use 'normal' text, and everything's fine. The 3rd and 4th line use 'ss11' and, by some mysterious reason, though both lines contain the same text, the line with the date field contains too much space behind the '1'. When checking the '1' in right-aligned text, the ss11 version suddenly doesn't have too much space behind it, but appears to have negative metrics at the right, so that it overlaps the frame. Checking the same with differently styled versions of the 'Q' character produces the same error: The 'normal' Q is correct, any of the styled versions has negative metrics. This definitely seems to be a bug in Publisher, because every other software I tried does this correctly. Affinity Designer 1.6.5.123 also yields correct results (no additional white space, proper alignment). If Publisher and Designer use the same code base for OpenType support, please revert Publisher to Designer's correct behaviour. Andreas Weidner
  4. Sorry to nag about an esoteric issue that is probably of no concern to the vast majority of DTP users -- to me, however, it is highly important that the automatic typesetting of long s in Gerhard Helzel's open type fonts function properly - which is still not the case with build 1.7.0.133 (win). If the automatic long s-function can't be implemented in Apub for some reason, I would have to continue to use Word, where this function works flawlessly, even as Word is rather clumsy to use in so many other aspects of DTP. But if this particular function works so well with Word, why can't it be done in Apub? Would seem to me that a skillful programmer could solve this quickly. However, as I am no programmer myself, I may be making an inference that is way beyond the scope of my knowledge, so please pardon me if I'm mistaken in this regard. https://forum.affinity.serif.com/index.php?/topic/67933-opentype-support/&tab=comments#comment-351320
  5. Hello, Are you planning on adding functionality for the new OpenType variable font technology in Designer, Photo and Publisher? Best, Bauke
  6. For instance, the below text:- (literally:- are you going this year, brother ?) is not rendered properly in both Designer and Photo. The area that I highlighted contains tone mark which is supposed to be a bit higher than the upper-level characters, However, they are placed at the same level, and clash with each other. This suggested that the OpenType GPOS table is not applied.
  7. Please add support for OpenType locl feature - Localized forms. Currently you can switch the language of a text from the Character palette, but this doesn't trigger the locl feature. (This is how it usually works in Adobe apps) This feature is quite important especially for Cyrillic scripts. Tested this with Affinity Designer, not sure what is the case with Affinity Photo.
  8. If a PDF with oldstyle figures is placed in an Affinity Designer document the figures get changed to default style (but with horrible kerning). If the PDF was orgininally created in Designer all numbers are changed to default figure style (as far as I can tell). If the PDF was created in Illustrator only the numbers of some of the fonts are changed. Look at the two attached files (JPEG preview and Affinity Designer): On top is the text written directly in Designer, below the placed PDF made with Designer and below that, the PDF made with Illustrator. The three fonts I used in this example should be ok (Adobe Jenson Pro, Minion Pro and Myriad Pro). Both PDFs look ok in Adobe Acrobat. Is this a bug or am I doing something wrong when exporting the PDF? Oldstyle-in-PDFs.afdesign
  9. There's a very specific combination of factors that causes this, but I verified in Illustrator that it's not just the font. I'm using the commercial font family Reatime, which is a monospaced font with an OpenType stylistic set that is proportionally-spaced. When the stylistic set is enabled in a text frame, certain combinations of letters (it seems random, but is replicable) result in a space wrapping to the next line, thus indenting the text on the new line. I can send a copy of the font for testing purposes to any of the developers.
  10. Hi, I do you have plans to change the opentype display in Affinity Designer. At the moment you cant see does a font support Small caps / superscript or does Affinity make a Faux version. Is there a email address where i could send questions about using Affinity programs at our school? We could be interested on installing Affinity suite on our Schools computers.
  11. Steps to reproduce: Create a line of text using the font FenoType Journey Open the Typography inspector Expected result: Font contains swash, stylistic alternates, and titling alternates (accessible in Illustrator)Observed result: No swash, stylistic alternates, or titling alternates options are shown in the typography pane I can send you a copy of the font for testing if you'd like.
  12. How do I access the extended character set in some of the newer Opentype fonts that have alternate swash caps, etc.? Illustrator has a glyphs panel, which I don't think AD has yet, but is there another way to do this, eg. keyboard shortcut or another utility? Thanks.
  13. Hi guys, Affinity Designer looks like a very promising alternative to Illustrator. I am a type designer (Proxima Nova) and have noticed some glitches in the OpenType support. The first one is in the display of Stylistic Sets in the Typography palette. Normally, these are displayed correctly, but I've discovered that if a font contains gaps in the range of Stylistic Sets, AD will only display Stylistic Sets up to the gap. For example, my typeface Proxima Nova contains nine Stylistic Sets. However, SS04 is only available in the roman styles, and SS05 is only available in the italic styles. (Background: These substitute an alternate lowercase "a" in the roman and italic, respectively. The roman has a two-story "a" while the italic has a one-story "a". If you prefer the one-story a, you can apply SS04 to a range of text and the roman "a" will change to the one-story design, while the italic is unaffected. The result is that the one-story "a" is used for both roman and italic. If you prefer the two-story "a", you can apply SS05 to a range of text and the italic "a" will change to the two-story design and the roman will be unaffected. The result is that the two-story "a" will be used for both the roman and italic.) Proxima Nova roman styles have no SS05, and Proxima Nova italic styles have no SS04. When using Proxima Nova in AD, the Stylistic Set listings in the Typography palette stop at SS04 in the roman and at SS03 in the italic. It seems that AD checks for each possible Stylistic Set (01-20) sequentially, but as soon as a Set index is not found, it stops looking and assumes that there are no more Sets in the font. There is no requirement that Stylistic Sets must be contiguous, as far as I know, so I believe this is a bug. No other software exhibits this behavior that I know of. Screen shots from AD and TextEdit attached. TextEdit shows all of the Stylistic Sets correctly.
  14. There are some very odd behaviours with the numerals. If I select all the text and choose Oldstyle proportional numerals, some of the numerals are lining. If I make one of the numerals tabular, all the numerals are Oldstyle. I have tried this with several fonts.
  15. Trying out Affinity Designer I quickly found a bug when applying the Opentype Small Caps attribute to text. As you can see in the middle line of the pdf-file attached, in no font I tried “ein” and “ext” (of “Texttext”) is correctly formatted, neither in most fonts the “t” of “ist” – only Satero and Espuma make a difference here. There seems to be a difference, too, depending whether you use Art Text or Frame Text, as you can see in the top line: Set as Art Text, “esttext” is in lower case – in Frame Text it is again “t”, “ein” and “ext”. As I have the font Granjon in both OpenType- and PostScript-Format I sampled the latter as well. Keep up the good work!
  16. Fantastic software! Many thanks. I am trying to set some Greek text using true small caps using various typefaces which I know contain and support true small caps for both Latin and Greek scripts. I have tried Arno Pro and Adobe Text Pro, and I suspect the issue is not with these fonts. Latin text set in true small caps from the 'Opentype' menu renders fine, but Greek does not. some characters turn into true small caps when writing but the input seems strange. I attach a screengrab showing the difference. Any assistance would be welcome. Many thanks in advance.
×

Important Information

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.