Jump to content

SamSteele

Members
  • Posts

    174
  • Joined

  • Last visited

Posts posted by SamSteele

  1. 6 hours ago, Eddie Aguirre said:

    I wanted to reach out to let you guys know that we've released IDMarkz SE for Windows

    We released IDMarkz for macOS just over two years ago. Since that initial release, we've been getting requests for a Windows version. It's taken longer than expected, but I'm happy to announce that we now have a Windows application. The Windows and macOS products do differ [IDMarkz for macOS vs. IDMarkz SE for Windows], but they both serve the same purpose, moving InDesign files (INDD) to other applications, including Affinity Publisher.

    Use Promo Code IDMSE for 15% off through January 2022

    Disclaimer:
    I'm a software engineer at Markzware, the company behind IDMarkz.

    If you have any questions, please feel free to reach out to me.

    Too bad it only works with WIN 10 & 11. A lot of us avoided 10 like the plague (a classic example of how trying to make something better made it worse) and stayed with WIN 7. I shudder at the thought of v. 11. People who adhere to Jobism please refrain from commenting. I hear your company makes telephones now. 

    Nice to see the promo code discount, though.

  2. Joachim_L wrote: You can try to install the attached files packed in a ZIP. How to install look at ...

    Thank you very much Joachim.  👍😄  This eventually worked for me after messing around for a couple of hours. The trick is to create 2 subfolders under the Dictionary folder: call the first "my Dictionaries" or something, and under that create another subfolder with the locale name xx_XX.

    For me this is:   C:\ProgramData\Affinity\Common\1.0\Dictionaries\AdditionalDictionaries\en_CA. The actual en_CA files are in the en_CA folder.

    In Edit > Preferences  > Tools (no document open) I chose my AdditionalDictionaries folder.
    AdditionalDictionaries.JPG.229c91fbc98c5b507e2ff964be276219.JPG
    This gave me access to the en_CA files in the en_CA subfolder. Now Publisher doesn't flag Canadian English spellings in an imported document as errors when spell-check or pre-flight is invoked. I believe that if I also installed more dictionary files, say en_US, they would be in their own en_US folder under the same AdditionalDictionaries folder. I only add the results of my efforts in the hope they will make it easier for some other poor sod to add a dictionary.

    Thanks again, Joachim!

  3. Publisher really needs a Canadian English dictionary. Millions of documents are typed in MS Word which has such a dictionary and is widely used in Canada to avoid US spellings of neighbour, colour, honour, etc. (I notice this app uses a US dictionary so those words were flagged.)

    Many Canadian English words are spelled the same way in UK English, and my preference is set to UK English, so why doesn't Publisher at least accept the same spelling? Oh no. The Affinity people have rigidly required that I go through every word in a submitted MS Word document that has words with the proper spelling to ensure that all spellings are tagged as UK English and not Canadian English. How very colonial. God help the poor French Québecer who doesn't write Parisian French!

    I've said before that AFF Publisher is not a productivity tool. Once again I am confirmed.

    Please, either create a Canadian English Dictionary or make the UK English dictionary accept Canadian spellings that are identical. Otherwise, your spelling checker AND your preflight app are untrustworthy.925586375_Colourdict.PNG.67146788723ca8d00e750d5ca55a99c5.PNG529653350_Languagedict.PNG.6f3397dfe78da01746ab418ce2d3df01.PNG

  4. 34 minutes ago, R C-R said:

    Thanks! That explains why I was getting different results on my Mac with the different apps -- I never really paid any attention to the CMYK hamburger 8 bit/percent options until you mentioned this.

    For CMYK, I would not mind if they always show percentage values & the top sliders always show 8 bit values. For RGB, I would like to see the top sliders show 8, 16 (or 32?) bit values depending on the document's color format. I would also like to see the percentage fields accept & display fractional values at whatever decimal precision the bit depth of the format permits.

    To be honest, I went back to my document where this occurred and I don't know how I got there. However, I'm glad to see the phenomenon has been given a good airing. I'm not sure if 4C print shops (or digital printers) can reproduce individual inks to 1 or more decimal places (i.e 34% magenta ink, yes, but not 34.2% or 34.25% magenta ink). Some printer will tell us, I'm sure. Always listen to your printer!

    Cheers.

  5. 28 minutes ago, walt.farrell said:

    Isn't Alfred's link (above) to their website? 

    I had found Viva's website. The "it" I was referring to (always tricky, that word) was a specific reference to importing INDD files directly. I agree with MikeW's assessment: "Their website mostly sucks as regards of pertinent and/or easy to find information."  Love 'em or hate 'em, that's one thing Adobe was good at: documentation.

    FWIW, I want to know the price of something before I enter into a buying sequence.

  6. 1 hour ago, MikeW said:

    I hope your doubts have been satisfied. But if Alfred's link doesn't satisfy you, I would be happy to take a new screen shot...

    Sorry, and no offense taken to your skepticism. I do normally include the title bar in screen shots and I should have above. But do note, I do have the ability and capability to fake a screen shot...(;^)

    While VD can open .indd and .idml, and can export back via .idml, VD is not a panacea of disparate application workflows. I am a firm believer that where/when possible, one should use the same application (and even same version of said application) as the client expects in return.

    I have used VD for some years/versions because of clients that use it and expect finished VD files in return, not as a means around using ID. VD does have some niceties, but operates a bit different than I am use to with my more typical QXP/ID work and always takes a bit of time for me to get in a flow working with it.

    I have never heard of VivaDesign before and there are precious few reviews of it, but I will accept what you say and let others comment pro or con. I don't want to download yet another software program simply to see if it does something new. I would rather read it's features in the official documentation and so far I haven't come across it on their website.

    Of course you could fake a screen shot, so could I but we don't do that here. I'm sure you will agree, some screenshots are more informative than others.

    Cheers!

  7. 20 minutes ago, Wosven said:

    That's a little bit rude, Mike know enough that we don't doubt when he explains something.

    Just check the site:

    http://www.viva.de/en/solutions/publishing-workflows-processes-production-types

    2021-09-10_073011.thumb.png.fee6ac55caa68234946daf03dabb4516.png

    No, It's not rude, just honest. What you have snipped only proves that VivaDesign supports IDML inputs or outputs, not INDD. See green box above.

  8. 14 hours ago, paco52 said:

    INDD import would be nice.
    It doesn't seems impossible.
    I have recently tested Viva Designer and it imports nearly flawlessly INDD files.
    Acctually, with the basic 100 € version of Viva Designer, one can open INDD files and export them in IDML

    On the VIVADesigner website it only says the IDML files can be imported from or exported to InDesign;

    "Due to the excellent Import and Export functions of the Viva technology, InDesign® documents w.e.f. version CS4 in IDML format can be imported and also re-exported to InDesign®.

    See: http://www.viva.de/en/solutions/adobe-indesign-user.

    See also:Snip below of http://www.viva.de/en/component/jdownloads/send/53-manual/128-exchange-with-indesign

    Do you have a reference that states differently?

    VivaDesign-IDML.PNG

  9. 6 hours ago, NotMyFault said:

    Taking a different road to a more targeted approach:

    • use frequency separation with 3px to isolate unwanted color issue
    • add B/W adjustment. Set blend mode to difference
    • merge visible (looks almost black but isn’t, use levels adjustment to better see )
    • hide helping layers
    • Set blend mode to add
    • adjust opacity to about 30% gives optimal result

    This preserves the fine structures.

    you may need to experiment a bit with px settings.

    BTW the HF layer shows that a low quality jpeg compression amplified the scan damage.

    (Amplified color cast):

     

     

    remove color from scan.afphoto

    Will give it a shot. Photo was as given. The person is now deceased. What can you do?

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.