Seneca

The picture says it all. (Text Frame Panel) MacOS Mojave 10.14.4 beta.

You need be be careful. You need to pick your fights. A lot of people have used Publisher for "important projects" without any problem but those who did so also accepted potential loss of information. In the end you know best whether a given project is worth the risk and whether you can recreate it using another tool if need be, time permitting.

You need to keep in mind that .indd is a proprietary file format. Nobody else knows how to import that except Adobe. Like nobody else knows how to import Publisher files except Affinity. That said, Adobe publishes IDML (inDesign Markup Language) file format and that what Affinity will use to import inDesign files to Publisher. So, rest assured that Affinity will import inDesign files but inDesign files will need to be saved out as IDML files first. They are already working on this but nobody really knows when this facility will be added to Publisher. I suppose when it's ready to be shipped.

Check your options in the Text Frame Panel, particularly, Insets, or if this is all 0 then you need to have a look at you styles, left left indent, etc. You could also select the text frame and click on the Revert Defaults button.

Well, have a look. By the way this same behaviour is observed both on Mac and Windows. Screen.mov

Tried that before posting this request and it doesn't work for me. That's why I'm asking about that. It seems very basic to me.

Is this command not available yet or I am simply blind? If it's not available yet could you please consider adding it. I find it very useful when working with pictures. Many thanks

Well, inDesign correctly relinks text boxes even if you change the design. That's the point. It should be automatic. In inDesign you tell a text box that it is a main story and it remembers that. Unfortunately, you can only have 1 main story in inDesign. I would love Publisher to beat inDesign and be able to deal with more than just one story automatically. As the things stand now you can have as many stories in Publisher as you like except that they don't relink properly. I would love to be able to say to each text box in master pages: you belong to Story 1, to another you belong to Story 2, etc. and the computer should relink each text box according to what story it belongs to irrespective of what page it is on because each box know what sort it carries. This would be awesome.

Thanks @Old Bruce Will try to reset Publisher and see whether that resolves this particular problem.

I'm not sure what has been fixed here. It may well be that I don't understand how this feature works. But as far as I can see this is still broken. Pease see the recording: Screen.mov

The field is black in dark mode when typing text.

@Uncle Mez, I didn't mean to be offensive in any way. FWIW, I have also done a few projects with Publisher beta and that helped me to discover bugs, etc. I completely agree that a concrete project is the best way to take Publisher through its paces. What I don't think is right though is to compare Publisher to Word (a released product) which had a number of file format changes and needs to keep a lot of people happy especially those with legacy files. Last thing we want is for the dev team to waste their time trying to keep previous formats in sync with the latest betas. The sand is still shifting under out feet and we beta testers have agreed to that.

You use these betas at your own risk. If you use it for production that is your choice. No, developers should not have to do that (Save as...).

Yes, it crashes on me too. I think you should send this file to the devs. They will delete it once they've identified the problem, and it may prove useful to them in identifying bugs, etc. Just report it as a bug.

Actually you don't. What you need is an ancestor style that will keep all common characteristics of TOC. So if you copy the specs from Base to TOC 1: Entry you have basically defined a common ancestor style from which other TOC styles are based off.

This PDF might be relevant to the discussion here: https://www.pdfa.org/wp-content/uploads/2017/05/PDFX-in-a-Nutshell.pdf

Those squiggly lines. Wait they have heads, arrowheads.

You may want to have a look at Preferences -> Colour particularly preferences for importing graphics or assigning colour profiles. If you set it correctly (the way you want it), then you know what your'e dealing with.

That's correct but then when you drag that master page over another master page and move your page over to the left or right page that page will highlight to let you know what part of the master page (verso or recto page) you are about to modify.

This is something I've been doing for a while now. But I'm curious why you think you can't do that and that this may cause problems in the future. Did you read it somewhere in the existing documentation or is this just your hunch?

Clearly not. What @Dave Harris said was: So put your dictionary in /Users/YOUR NAME/Spelling/dictionary type/dictionary But I agree that it would be great to be able to put a new dictionary in ~/Users/user/Library/Spelling/

I'm a bit confused what's your use case here is but remember that you can apply master pages to master pages and so you can achieve any permutation of master pages you want. Once you've done that you can then use these as your base master pages for your work. But like I said I'm not sure whether I follow you here.

I actually like the way it's done in Publisher, although I realise that this setup is great for books and and so much for magazines where you need to tweak things all the time. In another thread here in the forum I suggested to have a per text box customisation. This could/should be done on Master Pages where you could choose what behaviour a text box should adopt. This way one could easily emulate either QXP or inDesign way of doing things. With the added advantage that one could actually achieve a hybrid setup.

You can save these presets yourself if you so wish. Just click on the right burger icon next to the Page Preset as you create your own page size.

Automatic Hyphenation between 2 words separated by a Non-Breaking Space kicks-in when the minimum prefix is 1 or 2 and when the first word is composed of 1 or 2 letters. I think that Hyphenation should not be attempted between words separated by a non-breaking space anyway. The non-breaking space is used to prevent 1 or 2 letter words at the end of a line. This can be remedied by increasing the minimum prefix to 3 for example but my previous point is still valid. Please see below: Screen-hyphen.mov