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

lmarcos

Members
  • Posts

    59
  • Joined

  • Last visited

Posts posted by lmarcos

  1. Dear Serif,

    I would suggest you train your customer support properly to answer queries. After purchasing V1 as a business through reverse charge  (registered in the EU VAT VIES), I tried to purchase V2 back in January, while the 50% discount was still available.

    I'm copying here the reply I received.

    Quote

    Since you last purchased we have had a new system in place whereby all company purchases are made through our inhouse system! It is a requirement of our inhouse system to fill in all requested information for us to be able to place the order.

    Please note the change in our inhouse system does not allow us to place orders for Sole Traders any more unless you are a company. Therefore Sole Traders need to make purchase directly on our webstore.

    After answering the folling to that email, I have received no reply so far and it's almost two months now.

    Quote

    I can’t make a purchase without VAT through the web. And I need an invoice with no VAT in order to comply with current legislation. 

    You can call it sole trade or company, I have to fill a vat tax model quarterly and for this kind of purchase I can’t get a refund of vat since it’s not applicable. And the invoice I sent you already have the data you’re requesting if it’s not been transferred to your new system. 

    If I can’t purchase a professional software as a professional, I’ll stick to V1. 
     

    I'm currently experiencing problems with V1 (a file wouldn't allow me to save changes and another one isn't exporting italics), but right now I'm frustrated and wanted to get your previous level of support back.

  2. On 1/8/2021 at 4:05 PM, walt.farrell said:

    I am saying that as Affinity has no support for exporting HTML/CSS today, it is not as simple a matter as you suggest to provide the epub support. If they already had HTML/CSS support it would be less work (though still significant), but as they don't, providing HTML/CSS is a pre-requisite.

    And yes, it is something that all the applications will need, as they have a common core set of functions and can operate on each others' files. The good part of that is that only a single implementation of the function will be needed and it will cover all 3 applications.

    Shouldn't the CSS part be relatively easy? I mean, LO extensions like Writer2html from the Latex2html do it by adding the applied text styles to the css. The output problem of that css would be exactly the same as with anyother epub, limited support of certain css specs on many readers. Having a clean html would be much more difficult.

  3. On 1/18/2021 at 7:22 AM, Pogo said:

    Next - I have a Shutterstock photo - portrait with background - I used an iPad app called Photoscissors which 'cut out' the silhouette of the portrait and saved it to my Photos library (as PNG)

    Have you considered removing the background directly on Photo? You can either do it with the delete background or by selecting the silhouette and duplicating it in a new layer or something similar.

  4. On 8/13/2019 at 2:24 PM, Richard S said:

    Thanks everyone. I have now published a Kindle version as well as a printed version.

    My method was roundabout and probably not ideal, but used the tools I'm familiar with. It also seems to produce cleaner ePub encoding:

    1. Prepared the printed version using Affinity Publisher, exported this as PDF-x1a, sent it to the online printing service: Printed version looks good. :)
    2. Tried copy/paste of text from Affinity Publisher and from Adobe Reader, but found that the resulting unformatted text needed too much work. :(
    3. Imported the PDF-x1a into Serif PagePlus X9, in "flow" mode. This resulted in a separate "story" for each page, and put each page number into a separate story.
    4. Used "Edit Story" in PagePlus X9 to export each text story as a separate RTF file. Then re-assembled these using LibreOffice to produce a clean .ODT master file.
    5. In PagePlus X9, created a new iPad mini document, inserted the .ODT text file. Inserted the images. Tweaked & cleaned the text and formatting.
    6. "Published" the document from PagePlus X9 as a Flowing ePub3, adding a hyperlinked ToC. Previewed this using MS Edge. Made changes, then repeated this...
    7. Uploaded the ePub3 to Amazon KDP, uploaded the cover image, previewed the converted result using Amazon's online previewer, also downloaded the converted .mobi file and checked this using Amazon's offline Kindle Previewer software.

     

    Just a tip for you, LibreOffice can export directly to epub. If the output from the default export filter doesn't suit you, you can install the writer2html extension. You'll still need to tweak the css for some styles, but its output is rather clean ;)

  5. 1 hour ago, closen19 said:

    to be honest I didn't fully understand what the problem was ? are you looking for a photo editor? or what ?!

    The photo editor is Affinity Photo, and I wasn't able to find a way in the development persona to isolate an area and develop that with differente values than the main picture to recover the details on the white areas. I have to check the support forum, but wanted just to share the picture.

    Btw, looking at the picture now, I might be reframing it (tip for myself (; ).

    1 hour ago, John Rostron said:

    I don't think that the subject matter lends itself to a monochrome image. Just my opinion.

    John

    Which is fair, as far as opinions go. But even then, you don't learn how to use a program by only watching tutorials. For hands on learning any photo will do. And since I like the result, I share it here.

  6. Playing with the development persona and the RAW pictures taken directly with the app on the iPad, I came with this. I still have to explore how to apply a different development to a given area of the picture, but other than that, I'm pretty happy with the result.

    Anyways, if someone has tips to improve, they'll be quite welcomed.

    tradescantiaBN.jpg

  7. I have been playing yesterday with taking directly pictures from the Ipad on the AP and find the RAWs were mostly over exposed under direct sun conditions and quite different from what was shown on the preview.

    I don't take my entry level reflex to most sites, but I do take my ipad to some and take pictures for fun.

    Can you please consider adding ISO, exposure, shutter speed and WB controls for manual control?

    Thank you very much.

  8. 4 minutes ago, garrettm30 said:

    That's a good observation, but it is far limited compared to CSS.

    CSS has come far too complex lately for people like me who only use it now and then. And without the inspector on the web browser I would have had a hard time tracking the setting I had to override, so even if Apub is limited compared to css, it's more friendly for people like me... and I'm glad it is 😋

  9. On 4/7/2020 at 8:16 PM, garrettm30 said:

    There is nothing like the concept of giving a single element multiple classes.

    There's at least one point in which this is not true, though it currently has glitches. It is a paragraph style with drop cap and initial words. The first letter gets the drop cap character style first and the initial words character second.

    And you can have underline and bold without creating a new character style as well.

  10. On 4/1/2020 at 11:09 PM, MikeA said:

    character style based only on the underlying paragraph's attributes—

    Try Libre Office before purchasing a Word licence. That's how it works.

    Regarding the comment on character styles, you can set your own ones by clicking on the +a in the menu, either the one in the picture or a different one. You can set the font, font color, font style...  After fiddling around with Apub, my take is that those three are the ones that will map the default bold, italic and bold italic from any default bold, italic or bold italic you copy from other programs/documents, and only if you have the three styles for the given font.

    image.png

    Regarding paragraph styles, there is a no style (which is using arial font and I don't know how to change), a base style build over that and then body /body text build on top and equivalent to body text in word/Libre Office. Normal would be equivalent to Default Style. If you want body text to modify when normal is modified you need to manually link it to normal, because both are based on base style by default.

  11. 35 minutes ago, Gabe said:

    Character styles are not copied to clipboard, so they will not come through. I'm not entirely sure what you mean by "Applied directly".

    Yes, character styles from Libre Office are copied to clipboard and correctly pasted, except for small cap. Bold and italics are also correctly pasted when applied directly by clicking on the b or i buttons, provided you have a font including a bold and italic set. Small caps are not copied either way and have to be manually reapplied.

    35 minutes ago, Gabe said:

     

    On 4/4/2020 at 6:39 PM, lmarcos said:

    I have a font with several sizes. LO text is 12 pt and it's carried over to the 08 pt size.

    Which font? Liberation and EB Garamond work fine

    EB Garamond. EB Garamond 12 pt regular is pasted as 08 pt regular when that font style is installed. The Google font doesn't have the complete set of styles, so that may be the reason you're not able to replicate. The author recommends the font on Google for use on the web, so I did not installed the google font until aftwerwards I run into this issue.

    22 hours ago, lmarcos said:

    The standard set I downloaded from Google Font and the set with the other points from the designer site.

    https://bitbucket.org/georgd/eb-garamond/downloads/

    PS I'm wondering whether the Liberation Serif to Arial mapping might actually be default in LO to default in APub? 🤔

  12. Versales style is applied correctly to initial words in my document, @Wosven, so I'm not sure what you're referring to there.

    Regarding drop capitals, if you switch that character style to bold or italic, then bolds or italics are correctly applied regardless. Same happens with color: the color from the initial words style is applied.

    But when I open your file it doesn't keep line height. If you switch to no changes or any language, it's ok; if you switch to no language, then it changes.

    So at least character alternative and line height are not correctly applied. And the line height issue isn't something that appeared in the document originally created with 1.7.2. (back then it wasn't even possible to use initial words and drop cap at the same time, so this is an advance) and saved in 1.8.2. In a new document with 1.8.3 the line height problem appears when you apply at the same time inital words with small caps and no language.

     

    Let's see if the following steps to reproduce issues work for you on a vanilla document, @Gabe and @Wosven

    • Open a new document.
    • Create a character style with small caps.
    • Create a paragraph style with initial words using the small caps style you created before and use drop cap as well.
    • Add some text, apply paragraph style and see if the drop cap changes it's height when you switch language -> correction from default to none on character menu in the paragraph style.
    • Create a character style with tipography alternate set to 1 (i.e. Pali )
    • Create a paragraph style with drop cap using the previous style.
    • Add some text, apply paragraph style and see if the drop cap changes its appearance when you switch language -> correction from default to none on character menu in the paragraph style.

    I know most people won't work with no language correction in their life, but there are instances in which you want to keep the original text as is. I.e. old texts or dialects with lots of localisms in which you don't want to create an additional dictionary.

  13. 1 hour ago, Wosven said:

    Perhaps you can show us when the drop cap disappear, since it stays whatever language I set the style to.

    If you take a look at the afphoto file, the drop cap is different (I'm copying it below). You might need to reproduce with a font with salt applied, or download the pali font. I'm sorry it was not clear in the first email.

    This is the picture in jpg.

    language.thumb.jpg.23ef8238078ccf0a6bb4f617bd473034.jpg

     

    26 minutes ago, Wosven said:

    Looking at your file, I was wondering if it was possible to add a Catalan dictionary. If it's called ca_ES APub reconize the dictionary.

    dict_catalan2.zip 1.24 MB · 0 downloads

    This is majorcan, with all it's local difference and even the old wording, so I would get a lot of warnings in preflight with the modern catalan. ie, they use aumud instead of almud, ses illes instead of les illes and so on.

    26 minutes ago, Wosven said:

    And last, be carefull, there's an extra space in the number of your parts before the I: I–

    and, shoudln't you use curly quotes/apostrophes for the Catalan text? (I would use them in Occitan).

     

    dict_catalan.zip 905.21 kB · 0 downloads

    I would say there's a missing space after the number. I might end copying the text as plain text and reapplying formatting because I'm having a lot of problems by pasting the tales one by one after I revise the Spanish version of the text. Regarding the apostrophe, that's how they sent it to me, I didn't thought about changing it until you mentioned.

    Only thing I did regarding the original version was asking some other friends of mine whether in catalan they write dialogues and interrogations marks and such the same as in Spanish or as in French. For dialogues the answer was it's the same as in Spanish, but for interrogation marks is not that clear, one said only at the end, the other said it can be both ways.

     

×
×
  • 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.