-
Posts
1,549 -
Joined
-
Last visited
Profile Information
-
Gender
Male
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
garrettm30 reacted to a post in a topic: Horizontally docking palettes for Mac version
-
GripsholmLion reacted to a post in a topic: Colour Model Definition For Hex Values
-
Colour Model Definition For Hex Values
garrettm30 replied to Hangman's topic in V2 Bugs found on macOS
Thank you for spelling it out. And obviously, since Dan C was able to find some issues, that’s all that really matters. #101D64 is not a decimal equivalent, for D is not a numeral in the decimal system. It is still some hexadecimal value of some sort, but what? Also interesting, when I tried to follow your recipe (including using #2B48FF), the value changed for me too, but rather than #101D64 as you reported, for me it changed to #111C64. There is definitely something going wrong, but now the developers have been alerted. As a fellow user, I thank you for helping make this software better. -
garrettm30 reacted to a post in a topic: Colour Model Definition For Hex Values
-
Colour Model Definition For Hex Values
garrettm30 replied to Hangman's topic in V2 Bugs found on macOS
I’m struggling to see what you mean—not that it matters whether I can see it, since this is a bug report. But it might be clearer if you give a recipe or a demo video. Maybe part of the reason I am having trouble is following what you mean by “Hex values in Base 16,” since hex (short for hexadecimal) is by very definition base 16, so hex values should always be base 16. Also, I don’t see percentages in either view, but rather either the value expressed as decimal (from 0 to 255 in 8-bit color) or as hexadecimal (from 0 to FF in hexadecimal in 8-bit color). I do notice that the wheel view does show HSL (rather than RGB) in decimal on the bottom left and of course RGB as hexadecimal on the right. -
garrettm30 reacted to a post in a topic: Select Same > Font
-
garrettm30 reacted to a post in a topic: What would it take to get Affinity on Linux?
-
garrettm30 reacted to a post in a topic: What would it take to get Affinity on Linux?
-
PaoloT reacted to a post in a topic: Exporting to 72dpi/ppi by default
-
Alfred reacted to a post in a topic: Exporting to 72dpi/ppi by default
-
Exporting to 72dpi/ppi by default
garrettm30 replied to PaoloT's topic in Feedback for the Affinity V2 Suite of Products
I typically go for 72dpi out of tradition, but just to be clear, the formal definition of CSS is 96 pixels equals 1 inch (see MDN here for a good reference on units). To see it in practice, I whipped up this very simple demo on CodePen where I have four boxes where the width for each is defined according to different units. You see that on the web, browsers treat 1 inch and 96 pixels to be equivalent. https://codepen.io/garrettm30/pen/GRLjEJb -
garrettm30 reacted to a post in a topic: Indicate Non-Breaking Hyphen as a Special Character
-
Thanks for looking into it. I am fine with considering it a feature request. But as to the question of representing non-marking glyphs, I would point out that the soft hyphen is also visible and yet it currently is distinguished in this way. Also, some software calls the equivalent feature “Show invisible characters,” and in that case perhaps one could argue that the non-breaking aspect of the non-breaking hyphen is not visibly distinguished, but as Serif wisely named the feature “Show Special Characters,” it seems like distinguishing a special-case hyphen from the regular variety would not be any stretch to the paradigm. My suggestion would be to follow the same symbol used spacesa regular space is indicated with a dot and a non-breaking space adds to the dot a circumflex accent above it, and several of the other non-breaking spaces also use some variant on the circumflex. Therefore, my first thought would be to apply the circumflex above the visible hyphen. That seems to be consistent, but my preference here is not strong: any symbol at all would be enough for me.
-
Krustysimplex reacted to a post in a topic: Add option Paragraph composer
-
phps reacted to a post in a topic: Add option Paragraph composer
-
phps reacted to a post in a topic: Full-paragraph type composition
-
garrettm30 reacted to a post in a topic: Indicate Non-Breaking Hyphen as a Special Character
-
Thank you for that information, and by the way, I also appreciated the chart you made here: I haven’t gone to the great trouble to document all that you did, but if it is accurate and I am not mistaken, then non-breaking hyphen is the only special character available from the insert submenu that is not indicated with Show Special Characters. That would argue that perhaps this is just a simple oversight and hopefully easy to fix.
-
kenmcd reacted to a post in a topic: Indicate Non-Breaking Hyphen as a Special Character
-
Oufti reacted to a post in a topic: Indicate Non-Breaking Hyphen as a Special Character
-
PaoloT reacted to a post in a topic: Indicate Non-Breaking Hyphen as a Special Character
-
garrettm30 started following Managing Resources Question and Indicate Non-Breaking Hyphen as a Special Character
-
I would like to request that the non-breaking hyphen (U+2011, the character inserted by that name in the Text->Insert->Hyphens and dashes menu) be indicated as a special character when “Show Special Characters” is enabled. It is not every document that I use them, but I think it is the majority of them. For example, as my work is in French, I use them: In the French versions of B.C. and A.D. for eras: av. J.‑C. and apr. J.‑C., where the abbreviation should not be broken. In conjugations involving the “T euphonique” such as fera-t-il where the possible break should be preferred after the first hyphen rather than the second. As a personal preference, since I deal with Christian texts, in verse range references when they fall at the end of a paragraph, for example, (Matthieu 19.6-9). where I want to assure that -9). is not alone on a line by itself at the end of a paragraph. Since the difference with the regular hyphen and non-breaking hyphen is not visible, I keep second-guessing myself as to whether I have already fixed a given text, and the only way I know to check is to copy and paste into the app UnicodeChecker or just to reinsert it to make sure even if it was already done. I always keep Show Special Characters turned on, so I can quickly confirm what type of space I have, and it would be nice if I could do the same with hyphens (in addition to soft hyphens, which are already indicated this way).
-
garrettm30 reacted to a post in a topic: Please add finally 1 Bit Tiff (at least export in Photo) Support!
-
garrettm30 reacted to a post in a topic: Please add finally 1 Bit Tiff (at least export in Photo) Support!
-
Alfred reacted to a post in a topic: Add option Paragraph composer
-
garrettm30 reacted to a post in a topic: Add option Paragraph composer
-
Add option Paragraph composer
garrettm30 replied to Kambro's topic in Feedback for the Affinity V2 Suite of Products
If you mean something like kerning tables, those things have been in fonts for a long time. I don’t know much about the inner working of fonts, so I am probably missing something, but I don’t think OpenType gives us anything new in terms of justification. -
Add option Paragraph composer
garrettm30 replied to Kambro's topic in Feedback for the Affinity V2 Suite of Products
I’m trying to think how OpenType fonts can have any bearing on justification quality. Could you help me understand? In your recent comparison that you posted, those were examples of healthy characters per line count that is close to the ideal, such as you would see in a single column novel layout. In those cases, justification has more space to work out and tends to be better even on a line composer. There are still occasions where a paragraph composer would be advantageous, such as certain no-break sequences that have to be worked around, either automatically or manually, but yes, generally, a paragraph composer is of lesser importance in those contexts. In narrower column contexts, such as various multi-column layouts, acceptable justification is a greater challenge, and that is where a multiline composer could be a time saver. -
As stated, that is still to come in a future update:
- 12 replies
-
Add option Paragraph composer
garrettm30 replied to Kambro's topic in Feedback for the Affinity V2 Suite of Products
I have been asking for this for a long time (by which I mean to say that I eagerly desire this feature; I do not mean to disparage the other progress Serif has made in many other welcome areas). On smaller projects (those of fewer pages), I have taken to manually managing line breaks on a line-by-line basis in Publisher, and I am starting to feel that the end results are better than the paragraph composer in InDesign. But that can take hours for something like a short novel, and for the larger projects, I still go back to InDesign—and I complain about it the whole way. It is amazing how archaic InDesign feels now. -
Variable fonts support
garrettm30 replied to Athanasius Pernath's topic in Feedback for the Affinity V2 Suite of Products
In this context, it is mostly just a page load issue: one 46KB file for five faces. Font loading really does affect page load speed, and page load speed unfortunately does affect the number of visitors, especially as it is one of the weighted factors in Google search ranks. This point does not have much to do with why it should be in Publisher. -
Variable fonts support
garrettm30 replied to Athanasius Pernath's topic in Feedback for the Affinity V2 Suite of Products
I am on Safari, and I did download the font file that it grabbed to test it out. It is indeed the variable version. -
Variable fonts support
garrettm30 replied to Athanasius Pernath's topic in Feedback for the Affinity V2 Suite of Products
No, I need to correct myself. When I inspect that CSS file that comes back from Google, it loads up 35 font resources, but I realized that the src is the same URL for all of them, and it is one 46 KB font file that gets loaded. Maybe Google is dynamically providing variable fonts for browsers that support them? Pretty cool.