Jump to content

eluengo

Members
  • Content count

    63
  • Joined

  • Last visited


Reputation Activity

  1. Thanks
    eluengo got a reaction from Patrick Connor in Reporting Localisation Issues in Mac Publisher beta #384 (#376 #371)   
    Hi
    Some problems in spanish localization
    (Otherwise, a good translation into spanish!!)
    (1)  Texts too long..." Alcance: Documento"->Doc. || "Buscar en: Todos marcos de texto" ->Todos marcos txt ||  The second half of the conmuting button is not to be seen, but "Text Flow" in english version can be "Flujo de txt"  ||  texts in next two checkboxes is too long and too compact and small... difficult to read: probably simply changing "tabla de contenido" to "TabCont" or "TabDeCont" (ie. "Detener en siguiente TabCont")
    (2)  Propiedades button.... either button a bit longer or abbreviate Propiedades... with "Propiedades" (without "..."), or with  "Props..."
    (3)  Too long and difficult to understand "Retraso de la descripción de herramientas", can be abbreviated with "Retraso de ayuda herramientas"
    (4)  Instead of "Ampliar" in this menu, better could be "Expandir"
    (5)  Instead of "Cambiar interfaz de usuario" (difficult to understand what the command does, better could be "Ver/Ocultar interfase" or "Conmutar interfase"
    (6)  In this pop-up menu change "Valor Predet." with "Predeterminado", and also could be a polite image that all language options are capitalized, and not only both Englishes (GB and American) and German.... "Español, Italiano, Português, Français, Русский"
    (I apologize for the big screenshots.... has to do with retina screen capture, surely)
    Emilio
    (1)
    (2)
    (3)
    (4)
    (5)
    (6)
     
  2. Thanks
    eluengo reacted to patbaer in interactive pdf with form fields   
    form fields and interactive pdf export would be nice
  3. Thanks
    eluengo reacted to Old Bruce in GREP find/replace suggestions (split)   
    I would love this even if we only had Selection as a choice.
  4. Like
    eluengo got a reaction from Tom Schülke in Is there a way to....   
    Styles in afpub isn't really an easy thing.
    As doesn't in ID neither in Word or Pages.
    But in afpub the interface doesn't help so much.
    My personal solution...
    -- deleting all styles EXCEPT both "no-style" styles, the paragraph one and the character one (and I send you with this text an afpub file with THOSE styles' characteristics). AND making this the default Styles in afpub (selecting it in the little menu appearing from the upper right corner of theText-Styles panel).
    -- for every proyect.... creating (or not) a base page with the styles I will use (or not).
    -- understanding that every Paragraph-Style has a Character-Style implicitly, and that Character-Styles mean only modifications to this base Implicit-Character-Style (so... using any character styles to different paragraph styles will make the general style structure of the document confusing, cumbersome and sometimes with an erratic behaviour).
    I don't know if this can help you, but it was for me.
    Emilio
    A4v.estilo nulo[afpub].afpub
  5. Thanks
    eluengo reacted to elmonopascual in Print Persona   
    Hi all. What do you think about have a "Print Persona" to replace the print dialog box? With a preview in large size (not the small preview of the dialog box).
    In this "persona" you could perform all the pre-printing tasks that are currently performed in the dialog but in a more comfortable way.
    Even in the future, more advanced imposition options and other pre-printing tasks could be added to this "persona".
    I think that printing is an important part of the workflow and deserves to have a "persona" dedicated to it.
  6. Like
    eluengo reacted to servarcon in modo ingeniero, modo matemático   
    Me agrada mucho el software pediria que introduzcan una funcionalidad para Matematicos, ingenieros donde se pueda introducir formulas matemáticas, lo cual quita mucho espacio de difusión dentro de la ciencias 
  7. Thanks
    eluengo reacted to A_B_C in Footnotes/Endnotes   
    Visit any university library and you'll find that endnotes replaced footnotes long ago, perhaps in the 1950s. In the era before computers, endnotes were far easier to typeset. In todays world, their appearance at the bottom of a page is seen as clutter by most readers.
    While this might be true up to a certain point for academic publications in the English-speaking world (and while there is a certain international convergence in recent years), there are also cultural differences. German academic publications are still heavily using footnotes for reference purposes as well as for comments and clarifications. And while footnotes might be perceived as clutter from a typographic point of view (it can be incredibly difficult to typeset certain sorts of academic texts in a visually pleasing way), they are much more practical for readers. Personally, I don’t like reading a book from two ends.
  8. Like
    eluengo reacted to Pudens in [PUBLISHER] How about multiple footnote/endnote threads in upcoming Publisher?   
    Hi!
    Somebody can tell me about possibility to implement multiple footnote/endnote threads in upcoming Affinity Publisher?
  9. Like
    eluengo reacted to MAUSSIMI in Convert text to table   
    Can not convert text (with tabs) to a table?
  10. Like
    eluengo reacted to Afife in Restore image ratio   
    Hello,
    1/ What is the quickest way to restore an (embedded) image to its native aspect ratio ? (I don't have any external copy of this picture and after a lot of changes, I can't remember the original dimensions...).
    2/ What is the quickest way to "extract" an image from my Publisher document to get it on the desktop ?
    Merci !
  11. Like
    eluengo got a reaction from A_B_C in little bug concerning text boxes & other boxes   
    a little bug
    when stretching vertically a text box (or a group or collection of elements with a text box included), if handle (and box) exceeds page limits, suddenly the box disappears. When releasing the mouse  button it reappears where it shoud be.... (video)
    pantallazo 2018-10-15 a las 19.31.38.mov
  12. Confused
    eluengo reacted to JGD in Tables inside text frames - mandatory   
    Yes, those are all valid questions. And then there are users like me, who would be [more] actively participating in the Beta if they only had the time. It's extremely frustrating, as an old-timer beta tester, to not even be able to really put the apps through their paces, but such is life (and I am certainly representative of the people who will buy this thing – and I will, anyway, regardless of how incomplete it is; I am treating Affinity a bit like if it was a Kickstarter project – because a) I already bought the other two, b) I've been using ID professionally for almost 10 years now and c) I don't intend on leaving the DTP market any time soon).
    As for feature dependencies… Sure, we don't know exactly which are dependent on which, but we can take some informed guesses. Seeing how Affinity Publisher is based on the same codebase as Affinity Designer, the internal support for variable page sizes (which should be just a different, more specialized implementation of artboards, after all) must be there already in some form, as should be the option of having more than two pages per spread.
    It should be just a matter of exposing it via the UI, adding a spine indicator and getting the pages to snap nicely to one another (and that's yet another area in which Serif could one-up Adobe; I've always hated how when you change some page's size, the adjacent ones don't snap neatly to it automatically, forcing you to break your spreads apart and rejoin them…), and while I can appreciate that it might take a while to implement, it should be an absolute priority for a self-proclaimed “professional” DTP app. Otherwise, when it comes specifically to page management, it behaves just like a glorified text editor, am I right?
    And the same goes for in-line, anchored objects… No self-respecting designer would start more complex projects in Publisher if that meant they would take even more work to do than even editing a Word document. That would defeat the whole purpose of using a dedicated DTP app, and would make the amateurs/prosumers default to Word/Pages and the professionals default to InDesign/Quark. That's why this thread is so important, and why I'm guessing at least this feature in particular will arrive in time of the 1.7.0 GM release.
  13. Thanks
    eluengo reacted to allen57301 in Footnotes and endnotes   
    Hi everyone !
    such a lot of work on this excellent beta!
    so, my question is about footnotes and endnotes, a feature that is fully useful for several publications I publish. Is a roadmap for them in a next time?
     
    thanks!
  14. Like
    eluengo got a reaction from Vynce in button to "preview" pages   
    could be interesting to have either a button or a simple keyboard command to hide ALL... margins, squares containing text or graphics, grid, etc... so in a moment is possible to see EXACTLY how the page will be printed without the interference of all those unprintable elements.
  15. Thanks
    eluengo got a reaction from Alfred in hierarchical TOC, how?   
    OK
    all works more or less as I awaited (and lacking any help, I've seen the answers afterwards)
    BUT... something happens with the order in which the app finds the different frames with the text&styles which should be inserted when the app compiles a TOC (in my case it is not a continuous text, there are different frames with different chunks of text), because it showed initially an erroneus entry order in the TOC frame. The solution was to cut and then paste the text frame that appeared  in the bad order in the TOC. Sorry I don't have the screen images, because it happened with a long and repeated trial-error sequence.
  16. Like
    eluengo got a reaction from Fixx in Is it possible to package a project in Publisher?   
    packaging proyects is very interesting.....
    BUT.... like ID, a package needs that the receiver (self or other) uses a compatible version of the generating app (ID or whatever).
    for a propietary/personal use..... a good archiving policy is better than packaging
    for another/printer/typesetter  ’s use....... better an interchange format: PDF can be a better solution, or EPS, or SVG, or the like

  17. Like
    eluengo got a reaction from Fixx in Is it possible to package a project in Publisher?   
    packaging proyects is very interesting.....
    BUT.... like ID, a package needs that the receiver (self or other) uses a compatible version of the generating app (ID or whatever).
    for a propietary/personal use..... a good archiving policy is better than packaging
    for another/printer/typesetter  ’s use....... better an interchange format: PDF can be a better solution, or EPS, or SVG, or the like

  18. Like
    eluengo got a reaction from hawk in problems with diacritics   
    There is a problem when keying vowels with diacritics... accents, instead of "á" or "ä" results in... "´á" or "¨ä"
     
    (Cheers for the app!!!!!!)
  19. Thanks
    eluengo got a reaction from Alfred in hierarchical TOC, how?   
    I've identified theTOC ordering problem....
    If the frame containing a hierarchical superior (supraordinated) line is created or pasted after a frame with a subordinate text item also compiling for the TOC, the result is that this last frame/text appears before the previous existing frame/text (subordinated, theoretically).
    Solution is cutting and re-pasting this previous existing text frame, and after recompiling the TOC, the lines order is the correct.
    (reordering through the [Layers] panel has no effect)
     
  20. Thanks
    eluengo got a reaction from Alfred in hierarchical TOC, how?   
    OK
    all works more or less as I awaited (and lacking any help, I've seen the answers afterwards)
    BUT... something happens with the order in which the app finds the different frames with the text&styles which should be inserted when the app compiles a TOC (in my case it is not a continuous text, there are different frames with different chunks of text), because it showed initially an erroneus entry order in the TOC frame. The solution was to cut and then paste the text frame that appeared  in the bad order in the TOC. Sorry I don't have the screen images, because it happened with a long and repeated trial-error sequence.
  21. Thanks
    eluengo got a reaction from Mariusz go in light grey interface   
    Could be interesting a light grey interface, like in macOS?
    LightGrey interface makes me (and others) easier to locate and use icons/buttons/....
  22. Like
    eluengo got a reaction from hawk in problems with diacritics   
    There is a problem when keying vowels with diacritics... accents, instead of "á" or "ä" results in... "´á" or "¨ä"
     
    (Cheers for the app!!!!!!)
  23. Like
    eluengo got a reaction from Gear maker in Layer transformation   
    Beside "Mesh Warp" and "Perspective" I think it would be interesting to have a transformation command (really "deformation") like it exists in Photoshop's Edit menu.
    Not only permitting perspective deformation, also stretching or compressing in vertical and horizontal directions, free rotating, irregular edge transformation to adapt (correct) nonsymmetric perspectives, etc.
     
    Emilio
×

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.