Jump to content

Search the Community

Showing results for tags 'typography'.



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 & Discussions
  • 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 125 results

  1. Hi, Alex here from Druide informatique, editor of Antidote (https://antidote.info). Some of our users are requesting the ability to use both software (Designer and Antidote) simultaneously and as seamless as possible. How can we deliver that to our mutual users? Thanks, Alex
  2. I need to put a comma in a superscript text but Publisher is making it the regular size at the regular position. It's the same for other punctuation marks.
  3. Like everyone else, I am absolutely thrilled about the beta, and can't wait to see how it develops. One of the key reasons to use LaTeX or InDesign over Microsoft Word is their superior type composition. While Word simply dumps in text as it occurs, without regard to spacing or line breaks, these other programs look at an entire paragraph to remove rivers of type, reduce the need for hyphenation, and so forth, just as human type compositors do. In TeX, this is the Knuth-Plass Line Breaking Algorithm; InDesign has the Adobe Paragraph Composer (which it uses by default, but also has an option to turn this off with a single-line composer). Implementing this in Affinity Publisher would make it far easier to produce professionally typeset documents.
  4. I’m loving everything Affinity is putting together. Also will there be ‪an addition of type controls (leading / tracking / kerning )with the hot keys( option key + arrow keys) for ipad. Option plus left and right controlling the tracking and kerning. Option plus up-and-down controlling the leading like adobe hot key. ‬once learned this hot key in the adobe its been tough on ipad trying to keep ip my type placement speed with out it.
  5. I have attempted to lay out my Higher Functioning Autistic Spectrum Communication Guide on Affinity Publisher. The results are interesting. I love the control this package gives me over typography and the excellent column guides facility. I hope you like the results although I still have a lot to learn. Added a slight edit to give the poetry a separate demarcation on page two. I used the rectangle tool with reduced opacity and placed the rectangle behind that particular column. I was surprised to find that the 'send to back' function actually sent the rectangle behind the layers which were on the Master Pages and not just on the current page. So I had to send it back one layer instead. I'm used to a slightly different functionality on PagePlus but I'm sure I'll adapt. Aspergers Information.pdf
  6. Hey Affinity guys, Thanks for all your hard work and creating this lovely, lovely suite. Ive purchased all three pieces of software and love them so far BUT there is one thing ive noticed in Publisher, it might seem small but I loved the feature and have grown very fond of it with my typography layout …. 1: I need and cant find the option on the baseline grid to trap my baseline within the outer margin (from left to right) so the baseline is NOT visible outside the set margin (top,bottom,side to side). It is an option in Indesign and I was very fond of it, it makes my working document look cleaner and helps me see how objects will float outside the 'no go' margin areas in my working doc. Please can we have this tool added. Thankyouuuuuuuuuu
  7. I am in the midst of creating a multi-page test document and I am stumped trying to find a paragraph rules option. Is such an option available in the Beta? If so, where can I find it? Otherwise I really do hope it will be included in a future update.
  8. Affinity Publisher 1.7.0.174 on Windows 7, 64bit (German) can auto-correct standard quotes into typographic quotes, which is very useful and a more-or-less standard feature in all serious writing software. Unfortunately, it appears that it can only correct English quotes ("stuff" into “stuff”). It would be nice if the auto-correction would take into account the currently selected language and use the most-often-used quote characters of that language, e.g. (zoomed for better visibility, would even be better with a serifed font): English: “text” and ‘text’ (as is already done) German: „text“ and ‚text‘ French: « text » and ‹ text › (plus others). This should more or less work flawlessly with the double quotes, but might be undesirable with the single quotes, because here, a closing German single quote (looking like a 6) and a German apostrophe (looking like a 9) cannot be distinguished via the usual algorithm. The same is valid for French (it's easy for English, because there, both apostrophe and closing single quote look the same). My suggestion for an algorithm with which to discern closing quotes and apostrophes would be as follows (as far as I know, no other program does that): If a single quote is entered and the character before it is a space or opening bracket or similar, replace the single quote by an opening single quote (this is already done and should always yield nice results). If a single quote is entered and the character before it is not one of the above, replace the single quote by a closing single quote (this is already done and yields good results, but might be wrong if apostrophes are desired). (this is new) If a 'normal' textual character is entered and the character directly before it is a closing single quote, replace that closing single quote by an apostrophe. This would mean that in case of writing the words it's nice, the single quote would be replaced two times, but at least the end result would be correct... To make it worse, some languages support more than one type of quotes: E.g., since the usual German quotes don't look very nice typographically, most German books use »this type«. Therefore, it would be wonderful if the user could select the auto-correction characters language-dependent manually. One could either include a (rather long and tedious) list of supported languages (as in the screenshot taken from a German text processor, which only supports typical languages used by Germans and is therefore not enough), or offer some edit fields for the user to fill in, as is currently done in PagePlus (which is nice). Andreas Weidner
  9. Hi, I recently switched to affinity designer from AI. To be honest, it hasn't been the experience I expected. The most recent issue I am facing is the font rendering of Indic languages. Am I going the wrong way? Which settings should I use to render hindi content well? Please help. Attached are the screenshots:
  10. I'd love to have an "all lowercase" setting in addition to "All Caps" and "Small Caps". It is not uncommon for designs to use only lowercase text, so it would be a handy feature. I have had to do this manually in InDesign so often I lost count years ago, only to occasionally then manually restore all the uppercase letters when someone changed their mind.
  11. Hi, I am creating the letter F by connecting the two nodes in the red circle to create a single path that I want to expand from a stroke to a shape and export to FontForge. After trying everything on the list below, ‘join’ continues to connect the two other end nodes in the green circle that I don’t want to connect. Things I have tried: Select both nodes in the red circle and ‘join’ and 'close' Select both nodes in the red circle hold shift and drag until both nodes turn yellow Enable ‘snap to selected nodes’ then select both nodes in the red circle and ‘join’ ‘Join’ both nodes in the green circle, select again and ‘break’
  12. If one cares about the end typographic level, there is a serious issue, as far as I can see, with the drop caps feature in Publisher. The top of a drop cap should align with the tops of capital letters on the first line next to it. I haven’t tested every single font of mine, but most come in on various distances lower than that. Other than your standard Arial, only two fonts, Caslon and Bodoni are acceptable. I would not use the drop cap function until fixed. There is also a possibility to align the drop cap to the left, which works fine on some fonts/letters, however not at all on others… Other design software offer a possibility to fix this manually by adding a word space before the drop cap, then giving it a minus distance (as first line indent). But Affinity only offers the possibility to make the indent wider. This is one of the professionals’ trade tricks, but we need them
  13. For most fonts selected, the rendering of the font features is unhelpful and just looks bad. To reproduce, open the 1.7.0.249 beta version of Publisher, pick a font, and click the Typography button. I see the following on Windows 10 Pro 1803.
  14. moononthebones

    No OpenType superscript

    I'm using the font Basier Square (from here: http://atipofoundry.com/fonts/basier) in Affinity Publisher Beta, but the OpenType superscripts don't work or appear in the typography panel. I'm using Affinity Publisher Beta 1.7.0.257 on macOS 10.14.3; the problem also occurred in the previous beta. Using the same font in Affinity Designer 1.6.5 gives me the option to use OpenType superscripts and they appear correctly. Can you help me resolve why the two programs are running differently? Ben
  15. Publisher has problems using the integrated kerning pairs of Postscript Type1 fonts. It ignores them! I noticed this with extreme pairs like LT. In new OpenType fonts this works correctly. Not so with Postscript Type1 – no matter if the AFM files or only the font suitcases are included.
  16. Hi, I have tried alot to find out the text arching features like lower arching upper arching features in Affinity Designer as well as free transforming of texts but all in vain. Examples of which I have attached(taken from google). So far I have to use adobee illustrator to do these arching and transforming and take it back to affinity designer which is really time consuming. Is there this feature already or are you guys planning to release it anytime soon? Its a big let downbecause so important these features are
  17. It would be useful to introduce more advanced features, like Discretionary Ligatures that could be useful with fonts like Chartwell. https://www.fontfont.com/how-to-use-ff-chartwell
  18. Hello, It seems that Affinity recognises the Instances in a variable font. That is good. Also the contours of these instances are looking okay! The problems is with the advance width of the glyphs. These stay the same though-out all the instances. That is wrong. The advance width can also be variable and need to be addressed. Hope it helps! Thom
  19. Hello, We need and extra interface/panel for the variable fonts. All the 'visible' axes need to populate that, so we can fiddle around with these and get in realtime visible output on the pages. How these interfaces must look like? Maybe, for a start, just as Illustrator has now, with sliders? Later, more refined controls. Some axes are just on/off switches (checkboxes). Maybe a font with a two axes designspace should have a square view where the user can drag a location in and so control the two axes at once... (thinking out loud here) Thom
  20. When using the Artistic Text tool to type Hindi words (devnagiri script), ligatures are not properly supported even though ligatures are turned on in character options. This problem persists even when pasting in text that is correctly typed in another app (Notes). For reference, the second word in the image should show up as “श्रीवास्तव.”
  21. Hi, It wold be lovely to have google fonts browser integrated directly into Affinity Designer for iPad. So you can browse through type catalog and have search criteria like serifs, sans-serif, condensed, display etc... Also Adobe Type would be nice but i konow that is far fetched :) Cheers! Igor
  22. I see lots of typography-based feature requests for Affinity Designer. This is not surprising since a lot of us are designers using very mature Adobe software and text wrap, linked text boxes, bullets, columns etc are all essential features for layout. However, we have Photo for photo editing, Designer for illustration and [hopefully soon] Publisher for layout. I think a lot of these "essential" typo features are being requested because Publisher has not yet been released. Designer should not get these advanced type features because they are aimed at layout, not illustration. Typo features that should be in Designer, should be limited to artistic effects like envelope distortions for warping and advanced text on path. My rule of thumb would be "if I can use the feature to design a logo, then it should be in Designer, if it's needed for a brochure, then it should be in Publisher". If we look at the Adobe line-up... sure Illustrator has got a truckload of text features that allow you to do typographic layouts, but I think that's part of Adobe's failings. I have designers who work for me who make me tear my hair out when they insist on using Illustrator for a 20 page brochure – it's possible but it's not the right tool for the job. Then they go and design a logo in PhotoShop – again, possible, but not the tool for the job. (Illustrator REALLY lost the plot when they added multiple pages/artboards) I think this comes from the fact that for many years, Adobe has been adding features from other applications and calling them "upgrades". Instead of innovation and reworking old tools, we just get shared feature sets. This is exactly what I consider to be "application bloat". I hope the developers at Affinity don't give in to all the requests to add missing features to Designer, when these missing features are actually a request for a missing application. Please Affinity, keep your apps focussed, efficient, streamlined and well-considered. Please don't turn all of them into a Jack-of-all-trades. Your pricing is low enough to force me by Publisher if I need typographic features. I'm concerned that when Publisher comes out, customers will pick and choose which, single app they want based on a collection of broad features that satisfy 70% of their needs, and then complain that it's missing features. Rather, we should buy the suite and get all the features we need, than try to get one app upgraded to the point where we don't need the others. I guess my post could also read "Please speed up delivery of Publisher", or at least give us a few more teasers – even just a full feature list of version 1.0 so we can stop asking for what is already on its way. Thanks guys for great software. I'm very optimistic for the future – a future without the need to have Adobe software on my computer. (and great typographic tools in Publisher is the last stepping stone to that future) :)
  23. I couldn’t find any way to set the baseline of a text frame depend upon a typeface’s x-Height i/o it’s Ascenders. IMHO, it’s kinda essential for vertical aligning —sentence case or capitalised case— text blocks properly. Sorry for the screenshot, I’ve just tried to explain myself more clearly.
  24. I am trying to accomplish something I do in Illo all the time but can’t seem to do in affinity. i like to convert my type to paths, and then merge the shapes. in Affinity I have converted the text to curves and then used the add command but it still won’t merge. See image for the overlap not going away. its almost as if I am missing a step after I convert the type to curves. Anyone have the answer?
  25. 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
×