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

Wosven

Members
  • Posts

    4,129
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Wosven got a reaction from MikeW in Fonts allowed in a packaged file   
    In the first place, the Affinity apps shouldn't copy the fonts. That's simple.
    If users want to use the same fonts on another computer, they'll have to get a subscription (or it should be a secondary computer of the same user).
    Transtlation: APub users shoudln't even get those fonts on their computer via a package, unless they have a similar and active subscription that will provide the fonts.
     
     
    So, should APub users sue Affinity once they are sued by some subscription fonts service ? 🙄
    I just think this is an error in the package implementation that need to be corrected, not another convoluted way to complicate our lives.
     
    But, trying to export (again) the original file, I get this warning about restricted fonts:

    But the next step doesn't provide any way to disable easily any font to be copied, and certainly not to disable at once all the restricted ones:

     
    From the previous discussion, it's not easy to even see those fonts in the package, since they are hidden files for some users.
  2. Like
    Wosven got a reaction from lacerto in Fonts allowed in a packaged file   
    @R C-R
    Again, we already gave the answers, and you just need to read:
    pecially:
    And in the terms of use:
    That's only four pages long, and made easy for us, graphists and artists to read, so you should be able to understand
  3. Like
    Wosven reacted to StuartRc in Untamed   
    Full Vector Components of Tree Toolkit [T2]
    Tried to make each tree different
    Added a section of new branches that can also be used with the Camouflage Kits






  4. Like
    Wosven reacted to AffinityJules in Megan's Magical Menagerie   
    I can't leave it alone!
    Another story based picture.

  5. Like
    Wosven got a reaction from lacerto in Fonts allowed in a packaged file   
    Again, please read this FAQ where most usual questions (and yours) are answered:
    https://helpx.adobe.com/fonts/using/font-licensing.html
     
    And as said about ethical way of working: we'll always paid a special attention to copyrights and/or licences for fonts and images. (we can looks like killjoy doing this on this forum, but it's an important part of the job.)
    When working on occasional small projects like flyers, we'll ask the client for his fonts if needed (he should at least have the licences) or also buy them for further andbigger collaboration, or simply buy the choosen fonts for a project for him and us (if it's in the deal, if we create new designs).
    Another example: you can have a clusters of people working on more important projects, needing particular fonts, and you'll buy fonts licences only for their computers, while the other will use more generic fonts, etc.
     
    When working, you're supposed to know the laws (at least the ones for your activity). That's why you'll pay attention to images' copyrights, fonts' licences, ownership of a design you need to reuse, etc. We're not "victims", but must be aware of what we are doing. We usually trust our clients, and don't ask to "see" the licences or the invoices, but in doubt, we usually tend to replace fonts and images by other ones that won't cause trouble.
    Especially for small works, when "small clients" doublty bought the elements they provide (Oh Google image! I spend a lot of time checking copyrights or asking for the use of visuals, or asking clients to buy the visuals they want to use... Once they understand you'll double-check such things, they tend to behave and stop googling images or looting web site for images to put in their documents).
  6. Like
    Wosven reacted to lacerto in Fonts allowed in a packaged file   
    The key question is: why are cloud fonts distributed in the first place? Using (even temporarily installing) them is clearly a violation of the license so whenever the receiving party has a legal license (in case of Adobe Fonts, an active CC subscription), they do not need physical fonts.
    In the traditional context delivering purchased physical fonts for technical production-related reasons, e.g. for the purpose of printing a job that (for whatever reason), needs to be delivered open (instead  of using a print PDF with embedded fonts), is a more understandable act also when the receiving party does not have a license -- a requirement that a printer, too, should purchase e.g. a license to fonts costing about EUR 1,000 just to be able to print the job, is not realistic, and as mentioned, these kinds of "license checks" are typically never done. In practise this often HAS been a realistic situation, though [all involved parties having a license of their own], e.g. when using fonts from Adobe FontFolio, so inclusion of exactly the versions of fonts that have been used in the job just guarantees expected results.
    But the point is: the designer has purchased the license specifically for the used fonts, and the receiving party, even when not holding a license, is assumed to install the fonts only temporarily for pure production purposes, and then remove the fonts. Whether this really happens, is up to professional ethics, but I think that this has been the general practise. A license that permits this explicitly (like ones sold by Fontspring mentioned by Adobe above) is not common, but reflects well what happens in real life.
    On the other hand, in design context it is not uncommon that e.g. an illustrator hired for a project gets a license of their own for the physical fonts that are needed in the job and charges (at least partially) for the extra expense, or when having permanent use, makes an investment just adding the price to their other business costs. 
    For small jobs (e.g. posters) which need to be delivered open it is customary to convert fonts to outlines or rasterize them to avoid licensing and version issues, and this can be done (either at export time or more destructively as per object) also in Affinity apps.
    If this is compared to a situation where cloud fonts are used in the job, and to a rare need in modern production to distribute an open job with text as text (rather than as outlines or rasterized), it is not unreasonable to assume that a professional printer has an active subscription to e,g, Adobe Fonts (a cost of EUR 10 for a month). This is not a problem in design context, either, so temporarily activating a CC license to have access to fonts used by a design team consisting of several independent artits is a same kind of "problem" as a need to purchase some paper and ink when needed.
    What Serif does here is IMO unethical and unprofessional. The fact that a dishonest user can serialize cloud fonts easily by other means (programmatically -- without Serif's assistance -- easily even large collections of cloud fonts) is another thing, and here it largely applies that what counts is how these fonts are subsequently used. When physical fonts acquired this way leave the user's computer (even when embedded after having been illegally installed), they make an intentional illegal distribution (and would typically get easily caught). Affinity users are largely amateurs and semi-professional users who might do illegal distribution inadvertently.
    UPDATE: After all, fair competition is possible, as well:


  7. Like
    Wosven got a reaction from garrettm30 in EPUB export   
    It all depend of the type of file. It's suited to produce books with lot of text, and do a fine job of it (if compared to older PDF2HTML tools).
    It won't be so bad as PDF with lot of images, but using a dedicated tool to create epub is always better, of course.
    ID do a sad job converting to epub, if the original file wasn't produced with this intend, since we use tricks and special characters that can't be well converted to html.
    And publishing houses will convert the ID file without finesse... (at least, a big editor does it this way, perhaps some will put more time on this and get a better result).
     
    Doing epub is a job and need skills. Using converting tools should be the first step, if not using a dedicated one.
     
    1. You'll only be able to use the same fonts if you tell the app to use them, and preferably if you got the licences for this use...
    2. Pages are irrelevant in an epub, unless you do fixed layout instead of reflow, but in this case, PDF is better suited.
    3. Epub is suppose to reflow content depending of the setting of the device (use document's fonts or choosen ones, use document's size or set one, etc.), it's screen size, etc. It's like a web page or browser.
    4. Are those illustrations usable on a web page? If not, they'll be converted to other format, with possible errors if the app messed the 4 CMYK channels with the 3 RVB ones.
  8. Like
    Wosven reacted to kenmcd in Fonts allowed in a packaged file   
    It is ridiculous that the operating system font managers do not provide this information.
    But you are not alone in this on the Mac.
    Just this week a Windows user posted a similar request in the Microsoft Topography repo.
    The image I posted above with the all the Brix Slab Bold info is from FontCreator (Windows only).
    Any font editor is going to have a way to set the embedding and the license info (and view it).
    FontLab (includes Mac version) also has the same, but the FontCreator dialog is easier for anyone to understand.
    FontForge (free open source, and has Mac version) has the same settings, but the user interface is just painful.
    The Glyphs App Mini font editor for Mac should have the same settings.
    The best solution is to get a font manager which provides the info more easily.
    The two I use the most on Windows, MainType and FontExpert, both have an Embedding column in the tabular font listing view - so it is really easy to see.
    And both have font info panels which show the embedding info and the licensing info.
    One of the font managers for the Mac should have the same info.
    Mac font managers are $10-$20 from what I have seen.
    Please check them out and let us know back here which ones have this info.
    There is one one online tool I know of which does show this info - for one font at a time.
    OpenType.js Font Inspector - https://opentype.js.org/font-inspector.html
    But it is sort of font-developer-geeky in that it just shows the contents of various tables.
    Licensing info is in the: Naming table (name)
    Embedding info is in the: OS/2 and Windows Metrics table (OS/2)
    The Embedding setting is: fsType
    That setting will just be a number.
    The meaning of those numbers is here:
    https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype
    Best thing to do to avoid the issue is not buy or use fonts with stupid licenses.
    And not subscribe to cloud fonts services with stupid licenses.
    Stupid licenses = those which do not allow users to do normal things like send a package.
    In the real world I am sure when there is a last minute snag on a huge printing project which has some stupid fonts in it, of course they shut the whole thing down, and send the multiple GBs of files back to get the typos fixed. Right.
    It is nice to know that based on the info above at least FontSpring is honest and has a dose of reality in the licensing (about how people actually work).
     
  9. Like
    Wosven reacted to PaulEC in Export PDF as separate pages   
    I'm sure it depends on what you are doing, but in many years of producing various types of PDFs, I could probably count on one hand the number of times I have wanted to have two page spreads in a PDF! The only usage case I can think of would be for a few eBooks (eg, ones with an image spanning the spread.).
    I'd really like to know the logic behind this setting and why Serif consider all spreads to be more useful (?) or needed more often (?) than all pages output. FWIW, I've dealt with a number of pro printers over the years and none of them have ever wanted me to supply two page spreads (or, come to that, all the pages as single files nor as imposed pages!). They invariably want the PDF "as is" and they look after the layout for printing.
  10. Like
    Wosven got a reaction from Old Bruce in Fonts allowed in a packaged file   
    It's simply a list of fonts available by an Adobe service. You can decidz to enable it or work without.
    If enabled, the free version will alllow you to search in a list of fonts, activate the ones you want, and use them in the current document.
    If someone else need to work on the document, he need also to enable the service.
    For a subscribtion, more fonts are available.
    Those aren't Adobe fonts especially, Adobe have contracts with different foundries, like the one that produced Brix Slab.
    I didn't test it, but I think Suitcase provide a similar service (at least you can search for fonts from different foundries, not installed on your computer).
  11. Like
    Wosven got a reaction from nawkboy in Please add PDF/X-3:2003 support for RGB color space with flattened files   
    Today, people mainly send me files made with ID, after I send them technical informations. They can either download and install the provided colour profile and a joboptions (or follow the manual steps and screenshots), and easily export with the right settings.
    They are mainly agencies, so they should be use to this... but really, they are not better at following instructions than smaller shops 🙄
    At least, smaller shops are happy to learn to manage profiles and export settings, so they won't have to pay someone to convert/correct their files.
     
    Most coworkers use ID, so no problem with them and their files. Some marketing people use Affinity apps. We had to set up a specific workflow to correct and convert those files and finally get acceptable ones, we can use in the final tools.
     
    We woudn't mind adding specific "how to" and preset files if the apps were able to export correctly from the start.
    Others company needing correct files wouldn't mind either, since spending time checking files, and trying to give the necessary explanations to get the correct result can be tricky.
    As you can see is those forum, people use and think of as many pathes as possible to do the same things! But for debugging, we always need to redo the full path, and search for the problem...
    If I hadn't to check 3 versions of the same file when the graphist doesn't pay attention, instead of using the same process/preset as last time he send me a file, I could do more interesting tasks. I'm sure I'm not the only one that find sharable presets/profiles can help.
  12. Like
    Wosven got a reaction from Alfred in change column widths within a single row   
    Exactly. I've got combo of shortcuts I do simply right-clicking and hitting the keys looking at the keyboard (years spend using one, and I keep needing looking at it...), not needing to look at the menus.
    I suppose it's why some of us complain about too many clicks to do in those apps...
  13. Like
    Wosven reacted to Alfred in change column widths within a single row   
    That’s an important accessibility feature, so it should be available.
    It’s only easy to click if you’re using a mouse! With only a keyboard but no keyboard shortcuts you have to use the arrow keys to move the focus to the option that you want, and then press Enter to confirm your choice.
  14. Like
    Wosven got a reaction from Alfred in change column widths within a single row   
    That's the logical way, but for people who had to struggle and try to win against columns's width living their own live, in term of spend time, @carl123 's way can be the fastest
  15. Thanks
    Wosven got a reaction from immeemz in Publisher repeatedly crashing, almost immediately   
    De rien.
    Ça fait des siècles que l'on écrit avec une faute "évènement", car le premier dictionnaire ayant été imprimé avec les premiers caractères accentués n'avait pas assez de "é" et a utilisé un "è" (pas le temps d'en faire refondre), pensant que personne ne s'en rendrait compte 🤣
    Peux-tu... pas la peine, ça plante aussi chez moi, spécifiquement avec "Évènement", pas "évèmenent".
    Si je supprime la ligne dans les préférences d'autocorrection, ça ne plante plus (et ne corrige plus non plus !). Donc il y a bien un bug dans la correction auto, en Fr-fr et Fr-ca (?) .
     
    ======
    No problem.
    It's been written with an error "évènement" error for centuries, because the first dictionary to be printed with the first accented characters didn't have enough "é" and used an "è" (no time to recast it), thinking no one would notice 🤣
    Can you... don't bother, it crashes with me too, specifically with "Évènement", not "évèmenent".
    If I delete the line in the autocorrect preferences, it doesn't crash anymore (and doesn't correct anymore either!). So there is a bug in the autocorrect, in Fr-fr and Fr-ca (?) .
     
  16. Like
    Wosven reacted to immeemz in Publisher repeatedly crashing, almost immediately   
    Hi Callum, I'm just repeating this here because you are a moderator...the above/previous posts explain the issue.  It IS a bug but only reproducible if I type in the word: Évènement (notice the exact accented characters).  If I type Événement (notice the second accented "e" is a é instead of a è) then this does not happen.  If I type Évènement at any point in the document, it crashes now.  This is ok for now because événement is the preferred spelling of the word, HOWEVER, I hope that the program will not now start crashing every time there is a misspelling or typo. I much prefer the little squiggly red line!  
    Edited to add:  this only happens with the capitalized form of the word, as Wosven was able to reproduce (below). 
  17. Like
    Wosven reacted to immeemz in Publisher repeatedly crashing, almost immediately   
    WOW, I am mind blown.  
    You are absolutely right.  If I type "Événement" this does not happen, but it crashes immediately upon typing "Évènement".  Thank God a Francophone (I am guessing) noticed this. I had to go to the "Banque linquistique" of the "Office de la langue française du Québec" to find out how we are writing this word these days and I guess at some point the spelling of "évènement" was "rectifié" to "événement" and I missed that memo.  
    What is absolutely baffling is why a misspelling would make the entire thing crash. And why just this word?  The spell checker is flagging words that are not in its dictionary such as the names of our villages...Palmarolle, Dupuy and names of organisations such as Viactive...there are tons of "misspellings" in the document according to Publisher's spell checker, as well as several other occurrences of "évènement" in the document.  I have now tested this several times and I can type and add new text and update this document fine UNTIL I type "Évènement" specifically, but it always immediately crashes after I type that one word.  
    Weird!!  
    Thank you very much for helping.  This is still obviously a bug but you've allowed me to be able to continue working on the document at least!  Merci beaucoup pour ton aide, j'apprécie beaucoup!!  Bonne journée.    
  18. Like
    Wosven got a reaction from carl123 in change column widths within a single row   
    That's the logical way, but for people who had to struggle and try to win against columns's width living their own live, in term of spend time, @carl123 's way can be the fastest
  19. Like
    Wosven reacted to Chills in import MS Publisher files to Afinity Publisher.   
    Many thanks to  emmrecs01  but I think on reflection given these files were put together by amateurs and I will need to do a lot of reformatting and cleaning up of style, fonts etc. as well as fixing errors in translation that Wosven mentions I will be better off with the original text files and photos and a fresh Affinity Publisher document.
    I am 99.99% certain I can get the images and if the worst comes to the worst they can cut and past the text to a word file.  It is only a 65 page document.   

    I am  helping a local history group and it is non-commercial so I am doing it for love not money. This is the problem…. Paid professional work tends to be a lot easier because usually people know what they are doing and use sensible file formats….. OK… sometimes they do J
  20. Like
    Wosven reacted to Chills in import MS Publisher files to Afinity Publisher.   
    You are right they they may have lsot the base files. I don't mind them using Word badly.. I can fix that. All I would need is the text and images seperately.  In any case the publisher files would need proof reading... they are not as accurate as they could be re spilling and grimmer.  🙂

    I agree it is probably better they use something they know. In which case it will have to be Word. I will do the formating in Afinity Publisher.

    thans to all for the commments and suggestions.

     
  21. Like
    Wosven reacted to carl123 in Change default color of fill layer   
    For me it produces whatever my "foreground" colour is set to
    If I change the "foreground" colour to something else and then do...
    Edit > Defaults > Save
    the next time I start the app my "foreground" colour is the new colour I selected and a fill layer will use that colour (unless I change the foreground colour)
     
    Try changing your "foreground" colour to black and doing the "Save" mentioned above
  22. Haha
    Wosven reacted to carl123 in Replacing multiple images in a Publisher document   
    Tomorrow, if no one else explains what I mean
    things to do now
  23. Haha
    Wosven reacted to carl123 in Replacing multiple images in a Publisher document   
    There's method in my perceived madness
    Approach the problem from a different angle
     
     
  24. Like
    Wosven reacted to ElectricGutter in Replacing multiple images in a Publisher document   
    Good Morning,
    Is there a way to bulk replace image files in a Publisher document?
    I did the initial layout using linked jpegs. I now want to replace all the images with full rez tiffs.
    Adobe InDesign allows all images to be selected and then relink them to another folder.
    I've used the Resource Manager to replace single images. This requires you to choose the
    image you want to replace the original with. I want to select 75 to 100 images — choose a folder — and let the software
    do the rest.

    Thanks
  25. Like
    Wosven reacted to garrettm30 in Find and Replace Studio - Find field should have focus when invoked   
    When the shortcut to bring up the Find and Replace Studio is invoked…
    Good: If the studio is not open, it is first opened. Good: If text is selected, the studio is first opened if needed, and regardless, the text selection is entered in the Find field, but in such a way that the user may start typing immediately to replace it if desired. Good: If the studio is not open and no text is selected, the Find field has focus after the studio is opened, so that one may type in the Find field immediately. Inconvenient: If the studio is open and no text is selected, the Find field gets cleared of the previous entry but does not have focus. It is this last item that is inconsistent with the others and causes some minor inconvenience. When typing cmd-F, if the FaR studio is already open and no text is selected, then one cannot simply type cmd-F and start typing a search string, because that typed text will be entered elsewhere. Instead, the Find field in the FaR studio must be clicked into before typing, thus limiting the value of the shortcut. In fact, the shortcut in this case serves no purpose, whereas it could be useful to restore focus to the Find field so as to remove the need for the fingers to leave the keyboard. This is a familiar function in other software.
×
×
  • 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.