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

mandrael

Members
  • Posts

    18
  • Joined

  • Last visited

Recent Profile Visitors

778 profile views
  1. True 😅 But considering this they should have less bugs, better looking more modern software. Like Affinity has.
  2. Sure, V2 may contain not supported content. But better an save option, which removes the potential not supported elements than not have any openable document for V1. Rebuild via copy & past would be an option for small documents perhaps. In the end it's the choice of Serif, if they want to have compatibility between the versions. Adobe solved this via IDML.
  3. Yes, that's an option, since Publisher is good in importing PDFs, but still, a lot of information would be lost. If no save as V1 is available, this would be the only option. Rebuild from a pdf.
  4. Okay, that's a bummer. If the document was saved with Publisher 2 it's lost forever for version 1. With a "save as version 1" all would be good ...
  5. Hi, I'd prefer not to have the exact date in the document. Only month and year. I don't see a user defined option for the date in field settings. Is there a way with version 2.0.4? Best, Michael
  6. Hi, I noticed there is NO support for opening Publisher v2 documents with Publisher v1. Not everyone has upgraded or intends to upgrade to v2. So how can I save Publisher 2 documents that a Publisher 1 user can open it? I don't see it in the "save as" or "export" section. Thanks for your help, Michael
  7. Hi, set an anchor in a paragraph on page 55. Then write a text on page 7 "see details on page <anchor>". The placeholder shows "55", which is also a link. Then insert several pages before page 55. If the placeholder doesn't update the page number, there is NO workaround. This is just NO cross-reference. Best, Michael
  8. I found the issue. It wasn't the hyphenation dictionary itself, but the hyphenation restrictions in paragraph. The first one was "Max consecutive hyphens", when I set it to 4 the hyphenation of the custom word was done at the correct position. The second one was "Paragraph end zone" and "Column end zone". Both were set to a high number. I reduced to 10 mm and the last word, which also was that new custom one, was hyphenated correctly.
  9. I also tried that (ignoring the "1"s within the words). Without success. Did you already succeeded in adding own words to the Affinity Publisher hyphenation? Perhaps there is another way? In InDesign e.g. there is a menu item in "Edit" to add own hyphenations.
  10. Hi, I followed the Affinity Help section "Installing dictionaries for hyphenation": 1. downloaded the Austrian dictionary here: https://github.com/LibreOffice/dictionaries/tree/master/de (hyph_de_AT.dic) 2. saved it in ~/Library/Spelling/de_AT 3. the dictionary appeared in Publisher in the panel signs. part of file with modification: ISO8859-1 #################################################################################### # This is the hyphenation file "hyph_de_AT.dic" of the German dictionary # # according to the reform of 2006-08-01 (i.e. reformed or new spelling) # # # # Language: German (de AT) # # # # Version: 2017-01-12 # # New: using the COMPOUND feature for improved hyphenation # # New: list with over 69,000 words and compounds by Karl Zeiler # # # # Origin: Based on the TeX hyphenation tables "dehyphn.tex", revision level 31. # # http://www.ctan.org/tex-archive/language/hyphenation/dehyphn.tex # # The TeX hyphenation tables are released under the LaTeX Project # # Public License (LPPL) # # # # License: OpenOffice.org Adaptions of this package are licensed under the # # GNU Lesser General Public License (LGPL 2 or later) and are under # # Copyright by # # # # Authors: conversion author: Marco Huggenberger <marco@by-night.ch> # # revised conversion: Daniel Naber <naber@danielnaber.de> # # improvements: Karl Zeiler <karl.zeiler@t-online.de> # # # # Please note, this dictionary is based on syllable matching patterns # # and thus should be suitable under other variations of German # # # # HYPH de DE hyph_de_DE # # HYPH de AT hyph_de_AT # # HYPH de CH hyph_de_CH # #################################################################################### COMPOUNDLEFTHYPHENMIN 2 COMPOUNDRIGHTHYPHENMIN 2 # own definitions ki1ne1sio1lo1gie neu1ro1ener1get1ische ki1ne1sio1loge ki1ne1sio1login aku1pres1sur # Zusammengesetzte adverbiale Pr‰fixe da1her da1her1ab1 da1her1an1 da1her1auf1 da1her1aus1 da1her1ein1 da1her1nieder1 da1her1¸ber1 da1her1um1 da1her1unter1 da1hin1 [...] I also tried to add the custom entries in the Affinity package for testing purposes, but they were ignored. I would be important to have hyphenation rules for words Affinity doesn't know. Do you have any ideas what went wrong? Best, Michael
  11. Hi, I followed the help how to install new dictionaries and added some own definitions, but they are ignored by Affinity Publisher (MacOS). Could anyone describe how to add own hyphenation definitions manually? Like ki1ne1sio1lo1gie? I added the words below # own definitions ki1ne1sio1lo1gie # Zusammengesetzte adverbiale Präfixe ..... But it's completely ignored. I selected the hyphen dictionary in the signs menu
  12. This looks like a task for LaTeX. In my understanding it's a highly referenced text. You'll be able to do this via LaTeX and get a really good layout. It's not too hard to handle, sometimes easier than visual word processors if you're used to it. And it's made for a huge amount of text. Long time ago I used LaTeX for this project: https://de.m.wikipedia.org/wiki/Wikipedia:WikiReader/Laub-_und_Nadelbäume_Mitteleuropas I hope Publisher will get basic cross referencing like Word has. It's crucial for many documents.
  13. I short: Affinity Publisher 1.8.4 can't make a simple table flow to the next page like any basic word processor can do? And I can't do anything about it?? Best, Michael
  14. Hi, I agree, cross references are very important for any publication with a few more pages: Example: Table of contents ... insert cross reference and place the right number ob the page, where a heading is. And this would also be useful within normal text. This way wrong page numbers are avoided. A standard Word feature. It really has to be implemented soon, I mean really 🙂 I just moved documents from InDesign and miss it in every document. Best, Michael
  15. Genau das habe ich gerade gesucht. Außerdem fände ich Hilfslinien für eine Diagonalkonstruktion und Layouten nach goldenem Schnitt eine gute Idee. Diagonalkonstruktion: https://typo-info.de/diagonalkonstruktion-mit-variablem-satzspiegel/ Nachtrag: Die Drittelregel kann man mit Spaltenhilfslinien umsetzen: Ansicht, Spaltenhilfslinien einblenden Hilfslinien konfigurieren Spaltenhilfslinien: 3 Spalten, 3 Zeilen Stil = Umrandung Ränder = 0 Falls jemand noch Tipps für Diagonalkonstruktion hat, gerne. Bis dahin halt manuell mit dem Linienwerkzeug. lg Michael
×
×
  • 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.