Spellin Mistake (alettiin) how to fix?

[KMA]

I downloaded the Finnish language package and now I need help, how can the hyphenation of the words in the picture be corrected?how to fix?

[Komatös]

Hello @KMA and welcome to the forums.

Double-click on the misspelled word in the checklist. You will be redirected to the page with the incorrect/unknown word.
Right-click on the incorrect/unknown word. 
You can now replace, ignore or learn the incorrect/unknown word.

[KMA]

Thanks, I'll try it right away.

[MikeTO]

This is odd because from your previous posts it looks like you're using macOS, but if I type those words into Publisher and set spelling language to Finnish, only two of the words are flagged as misspelled.

There is a bug in Hunspell which cause words in the dictionary to be flagged anyway, but not this many.

The Finnish Hunspell dictionary is already installed in macOS. Did you install your own and override the standard one? That could be the issue.

[lacerto]

Obsolete.

 

[thomaso]

22 minutes ago, lacerto said:

These errors do not appear to occur in context of Frame text.

It can also happen with Frame text, for instance:

[lacerto]

Obsolete.

[thomaso]

1 minute ago, lacerto said:

perhaps it is somehow language, and also OS version dependent

I suspect that, in addition to the app and operating system versions, it may also depend on the language settings in macOS, where the system language set may conflict with or influence the app/interface language set for Affinity with consequences for its handling of a text language. (Affinity appears to assume that OS + app language are the same.)

[MikeTO]

5 hours ago, lacerto said:

I think this might be related to an issue that appears (I think that only) on macOS version of Affinity Publisher, and having text in Artistic text layers. At least when the OS display language is not Finnish (e.g., I have it set to US English), the Finnish dictionary appears to be internally assigned incorrectly.

In addition, for English text, the dictionary is set as "en-FI" (English dialect in Finland?), for which there is naturally no dictionary:

When the text is set to be Finnish, basically all text in an Artistic text layer gets flagged as misspelled (both on canvas and in context of Preflight, if spelling check is included). The problem appears to be resolved if all affected text is selected and the Spelling language is reassigned as Finnish (Suomi). The reason for the failure might be that the Finnish text in an Artistic text layer is auto-assigned to something like fi-FI (which is basically correct, but on macOS the Hunspell dictionary for Finnish might be encoded differently e.g. fi_FI) so while the language is correctly recognized as Finnish so that spelling errors are triggered, only the reassignment gets the correct dictionary linked.

These errors do not appear to occur in context of Frame text.

There is no difference in language handling between the different types of text objects so I think that's just a misleading clue.

What is likely happening is this:

• Text that you create in Affinity with spelling language set to Finnish is being properly set to fi_FI
• Text that you copy from other applications (Safari, Mail, Notes, etc.) to Affinity is being copied as en_FI because that is the way you have your computer configured

To avoid this, you will need to reset the language or apply a text style to all rich text that you paste from other applications.

[lacerto]

Obsolete.

[thomaso]

28 minutes ago, lacerto said:

But I do not understand where the silly language definition itself, "en-FI", comes from, since it basically means "English in Finland" as if such thing existed as a kind of a dialect or official language (similarly as sv-FI, as Swedish is second official language in Finland). Does macOS really allow specify something like this?

I am not sure if indeed macOS allows this or whether Affinity creates such a language setting. This confusion exists in Affinity for years:

I never understood in what way a language combination like "en-DE" (or "en-FI") may be useful decision "by design" as indicated in this response:

On 8/18/2020 at 4:52 PM, Gabe said:

For English app language and any OS region, the default spelling should be "unknown en-{osRegion}". If one has a "dual language" setup (en-{language}), they need to install that dictionary. 

Interestingly the last Serif response in that longer thread expressed this behaviour as >>a pretty "safe" assumption<<.

On 9/16/2020 at 11:24 AM, Gabe said:

With an app language in English and a system region of Spanish, it expects a "en-ES" dictionary. I think it's a pretty "safe" assumption, based on the OS region and the app language.  

Finally I was able to stop this oddity for me by saving/overwriting the app 'Defaults' with a specific text language setting and thus to avoid the conflict caused by my German macOS + English Affinity UI:

[lacerto]

Obsolete.

[MikeTO]

macOS and Affinity will accept spelling and hyphenation dictionaries named fi-FI or fi_FI, both will work fine. This can't be the source of the problem.

You can set your defaults to any language, and spelling language is a combination of language and region. If you see a Preflight warning that the en_FI dictionary is missing, that's because there is no such dictionary and you have at some point placed text that was encoded as language=English and region=Finland. It is annoying but it is a logical system. It's easy to fix, just set language to Finnish and it will go away.

But if you find that creating art text keeps doing this but frame text works okay, it's because you saved your defaults after placing working with text encoded as en_FI. This would be annoying. It may seem like a but with art text but it's just because Affinity has two separate sets of defaults which is an ongoing point of confusion. In my manual I wrote:

Publisher has separate default formatting for text frames (standard text frames, shape text frames, and tables) and for text objects (art text and path text). When you save the current formatting as the default, you are saving changes to both text frame and text object defaults at the same time.

...

To set the default formatting based on formatted text:

1. To set the defaults for text frames (including shape text frames and tables) to match existing formatted text, choose the Frame Text or Table tool.

To set the defaults for text objects (including art text and path text) to match existing formatted text, choose any other tool such as the Artistic Text or Move tool.

2. Position the text cursor in the text whose formatting you want to set as the default and choose Edit > Defaults > Synchronize from Selection or click the matching icon in the Toolbar to set Publisher’s session defaults to match the text’s formatting.

To set the defaults for text frames and text objects, repeat steps 1 and 2.

3. The defaults for new text frames and/or text objects in this document will now be changed. To save these session defaults as Publisher’s defaults for new documents, choose Edit > Defaults > Save.

I recommend creating a new document before setting defaults, it will avoid a lot of confusion. You can also do a factory reset to get rid of any formatting you had saved as the default.

Good luck

[lacerto]

Obsolete.

[thomaso]

10 hours ago, MikeTO said:

You can set your defaults to any language, and spelling language is a combination of language and region. If you see a Preflight warning that the en_FI dictionary is missing, that's because there is no such dictionary and you have at some point placed text that was encoded as language=English and region=Finland. It is annoying but it is a logical system. It's easy to fix, just set language to Finnish and it will go away.

The question appears to be why Affinity uses a combination of its app language + the system language for spelling at all. It may base on a certain consequence but does not appear logical in terms of useful if it results by default in a missing dictionary for a language that might not exist (e.g. English as Finnish 'dialect', different to e.g. American as English 'dialect'). Affinity is aware that it offers less UI languages than the operating system.

From that perspective it appears more logical if Affinity would ignore a system setting as its spelling language (while considering the region makes sense for its UI decimal separators) AS SOON it can't offer an according dictionary, but instead would rather create a default setting that ignores its own app UI language to avoid its 'default' conflict of a missing dictionary that the app can't obviously find in the system or deliver with its app package.

With other words, I would expect Affinity to complete its process of language detection (a combination of system settings + its own app UI language) and auto-create a default that matches an available dictionary* … and thus auto-executes the step that we need to do manually as a solution of the conflict: "It's easy to fix, just set language to Finnish and it will go away."

(*or asks to the user to install a missing dictionary as soon it notices a possible conflict caused by a user's change of the app UI language after app installation or a system region setting that has no equivalent in the available Affinity UI languages.)

[MikeTO]

8 hours ago, lacerto said:

I can see that it is logical for you. All's good in macaffinity land then.

I do think the system is logical, once you understand it, but there are several issues which unfortunately combine to make Affinity difficult to set up for non-English users who must use English for the interface language.

Issue 1: The default spelling language for text created in Affinity defaults to your computer's interface language. If your computer's interface language is not supported by Affinity but you have other preferred languages, it will set spelling language to the first supported language in your preferred list. If there's no match at all I believe it sets it to English. I think spelling language should be changed to default to your computer's interface language, not to Affinity's UI language.

Issue 2: There are two sets of text defaults. As I mentioned above, Affinity has separate defaults for text frames and tables versus art text and path text. A new user who finally figures out how to set their default spelling language to Finnish is unlikely to realize that they've set the default language for just text frames or just art text. And they might inadvertently save their defaults with other attributes. This should be easier.

Issue 3: Affinity doesn't bundle many spelling dictionaries. IMO, Affinity doesn't come bundled with enough dictionaries. Adobe and Microsoft bundle almost every dictionary while Apple bundles a modest set and Affinity for Windows bundles a very limited set. This forces users to install their own dictionaries, frequently unsuccessfully. I realize that package size is an issue but this should be easier.

Issue 4: There's no automatic language detection.  I don't know if this is a real issue but users expect it to work like Microsoft Word. If you paste en-FI text into Word, Word will just convert it to fi-FI because it's smart enough to know that nobody types in en-FI. I'm not a big fan of this because I don't like my apps doing things on their own, but I can understand how a feature like this could make things simpler for Affinity users.

I will add a new section to the start of my manual to provide instructions for how to set up Affinity for users in countries like Finland. The information is already in the manual but you have to seek it out so I'll put it into an introductory section.

Good luck

[lacerto]

Obsolete.

[MikeTO]

I completely agree with you that installing Affinity onto a Finnish computer will result in a poor default spelling language. It shouldn't work this way.

I can't find any issues with copy/pasting from Word to Publisher on macOS so perhaps there is a Windows-specific issue. A few bugs with copy/paste from Word have been recorded recently for both platforms so it wouldn't be surprising if there is an issue with spelling language, too. If you could please share your test docx file here then a couple of us could take a look. I will review the docx to see how it's encoded and another Windows user could try to duplicate the copy/paste issue.

I've attached a small test file. I created it with LibreOffice and not Microsoft Word because Word prevents me from formatting text as English-Finland. Opening this in Word will convert the en-FI paragraph to en-CA (for me) or perhaps English-US or UK for others. This docx file places into Publisher exactly as I formatted it in LibreOffice, and if I copy/paste from Word it comes in exactly the same, except for the en-FI paragraph which was already changed by Word to en-CA.

test.docx

 

[lacerto]

Obsolete.

[MikeTO]

7 hours ago, lacerto said:

It seems that you did not watch the video clip I posted above where copy pasting from macOS Word to Affinity Publisher 2 results in incorrect language assignment, while copy pasting from Windows Word to Affinity Publisher behaves as expected. On both OSs I have US English as display language and Finnish regional settings. I can reproduce this consistently. I cannot see how changing the default language settings in Affinity Publisher could correct this in a situation the source text has multiple language assignments, because the receiving container gets a single language assignment, so basically max one language could even theoretically get correctly assigned. 

If you cannot experience anything like this, your deduction seems to be that errors other people are experiencing are results of their poor understanding of how Affinity apps operate, or the odd combination they have between their computer or app display language and their native language (implied by regional settings they have active in their OS). My deduction is that this is yet another glitch and inconsistency in Affinity apps and something that requires workarounds and specific user attention until it gets fixed (and it seems, fixed by Apple since at the moment I cannot get Pages work properly, either, in context of such dictionaries as sv-FI). 

Our disagreement seems to based already on different staring points since you appear to cherish ability of a user to define any arbitrary language-country combination for text, disregarding whether there is a matching language dictionary installed (or whether such dictionary actually even exists anywhere in the universe). I see no point in such virtual computing and would rather have computer programs be able to use something that actually exists and is installed and which other apps designed for similar purposes already can utilize.

I did watch your video clip. I'd still like to see the docx file.

The Affinity display language has no impact on pasting text into Affinity, it's only impact, beyond being the display language, is setting the default spelling language - this is the "factory default" which you can change. You really should change your default spelling language for both frame text and art text if you have not yet done so. But changing your default spelling language will have no impact on pasting text from Word.

I believe there can be a problem, but it's hard to tell what's going on in the video so having the file would help. I'm only trying to help you.

Regards

[MikeTO]

For Serif: I hope the issue with setting the default spelling language can be looked at because Affinity is quite difficult to set up for those who don't set type in one of the default languages. I wrote the following instructions for my manual:

1. Create a temporary new document; its settings are unimportant because it will be deleted when you’re done. [*** I added this step to avoid inadvertently saving other formatting they were experimenting with as default]

2. Choose the Frame Text  tool.

3. Using the Character panel, set Language > Spelling to the language you wish to use. If the language is not listed, refer to Installing additional dictionaries on page 317.

4. If you want to set the hyphenation language at the same time, set Language > Hyphenation to the language you want to use. Refer to Set the default hyphenation language below before changing this option.

5. Choose the Artistic Text  tool. [*** you must set spelling language for frame/shape/table text and art/path text separately because there are two sets of defaults]

6. The language you selected with the Frame Text tool will still be selected but select it from the list a second time. If you do not select it a second time the selection will not be saved. [*** this is counterintuitive. The language you want is already selected but you have to click the list and "select" it again or else when you save your defaults only the frame text language will be saved.]

7. Choose Edit > Defaults > Save to save the session defaults as Publisher’s new defaults. You can now close the temporary document.

[MikeTO]

One more note about international users having to set their spelling language twice for frame text and art text - owners of the suite need to do this separately for each application, selecting their language six times in total to replace English as a default.

[juanmanuel]

Here chiming in. IMHO, there should be an option to make the UI language independent of a a document's content language. Going even further, it should be possible to assign non-globally a language. Use cases are quite a lot. As of right now, it is either ignore gazillion pre-flight issues, or change a gazillion times the user interface language and tick lots of ignore issues.

Certainly not an ideal situation.

In my case it is an English and Spanish combination. Spanish, as is spoken in Mexico. Which, mind you, has it's quirks just as US of A English vs GB English. On that note, there is no Mexican Spanish included dictionary, which further complicates things.

I use Affinity with it's interface in English, and most text-related content in Spanish (Mexican). As it is right now, I prefer to completely ignore spelling errors, as to do a spell check I need to change the interface language, see if everything is correct. Then switch the interface language back again.

So, the TLDR version: Make text thingies have their own language attribute. Just like paragraph style, colour, etc. It would make things much more flexible.

[lacerto]

Obsolete.

[MikeTO]

4 hours ago, juanmanuel said:

I use Affinity with it's interface in English, and most text-related content in Spanish (Mexican). As it is right now, I prefer to completely ignore spelling errors, as to do a spell check I need to change the interface language, see if everything is correct. Then switch the interface language back again.

If you use Affinity in English, you can just set all your text to Spanish (Mexico). If you haven't already, download the two es_MX files from this page: https://forum.affinity.serif.com/index.php?/topic/98911-how-do-i-add-additional-dictionaries-to-affinity-publisher/

Then set your default spelling language using the steps I shared above and all your text can be spell checked as Spanish (Mexican) even if you use Affinity in English, with no need to ever change the interface language again.

4 hours ago, lacerto said:

1a) On Windows, pasting text directly on canvas (not in.an existing text frame) creates a single frame text layer with continuous flowing text with multiple language assignments of the source text (e.g. from Word) correctly retained, including footnotes. The behavior is identical when importing a Word document. Source language assignment sv-FI (for which there is support in Word, and which is also installed as a Hunspell library so that Affinity apps can access it) is correctly recognized in Publisher.

1b) On macOS, doing the same creates in Publisher multiple Art text layers (text rows) where the language is determined by the OS primary language (in my case US English), and it seems, the country part determined by the OS regional setting, so in my case en-FI, which is something that does not exist in real world as a language dictionary. In Mac apps like Pages the error does not happen because there is autodetection: Pages does not detect sv-FI (even if it is installed as Hunspell user dictionary), but it detects Finnish and English correctly. 

That is interesting. The Mac and Windows clipboards have different formats so it's not surprising there are some different results but note that you'll get different results depending on which tool you have selected when you choose Paste - this feature is barely mentioned in the Help system and I haven't added it to my manual yet.

With the Move tool: Paste will result in separate art text objects for each line of text as you reported. Word copies RTF, PDF, and plain text to the pasteboard and it appears that Publisher uses PDF when Move is selected because paragraphs are separate lines of text in a PDF file. This might have been a good choices for Designer but it's not for Publisher. For me, the language for each art text object was set to en_CA regardless of what I chose in Word and regardless of my default spelling language for art text in Affinity. I think the language is because the PDF lacks a default language so it's using the OS language but I don't know for sure, it's just a guess.

With the Text Frame tool (or Table tool): Paste will result in a text frame exactly half the size of the page in the centre of the page and the language. The languages for the pasted text exactly matched what I had chosen in Word. I assume this is similar to what you get on Windows with the Move tool, too.

With the Art Text tool: Paste will result in a single art text object exactly the right size in the centre of the page. The languages for the pasted text exactly matched what I had chosen in Word.

5 hours ago, lacerto said:

On macOS the language assignment sv-FI is not recognized so Preflight warns about missing sv-FI dictionary, but the text is mapped to macOS "Svenska", which works practically just fine. As mentioned, Pages cannot do this. 

If you want Publisher to recognize sv_FI you can install the sv_FI dictionaries and the Preflight errors should go away. macOS bundles sv_SE and fi_FI but sv_FI is available for download from the same link as I shared with juanmanuel above.

5 hours ago, lacerto said:

A freshly created Frame and Art text layers get the language from "No style" which in the Windows version is Finnish (fi-FI) but on macOS version "English" (en-FI). I have "Base" style on both platforms defined as Finnish (on Windows "Finnish (Finland)" and on macOS the OS based "Suomi"), so all my text styles based on "Base" have Finnish as the language setting on both platforms. I have not found a way to explicitly define language for "No style" on either platform, so I am assuming that Affinity apps determine it from the system, but differently and getting different results.

Here's how it really works:

• The app's default spelling languages for text frames and art text are inherited from the interface language. You can change the app defaults for both frame text and art text with the instructions I provided above.
• When you create a new document, the document's default spelling languages for frame text and art text are inherited from the app's defaults.
• When you create a text frame or art text, the default spelling languages are inherited from the document's defaults, they're not actually coming directly from the app's defaults.
• The document's defaults are updated whenever you choose a spelling language while working in the document and they are saved with the document.
• Even if you change the spelling language for all of the text in a text frame or art text object, the frame or object still has its default language. Choosing Edit > Default > Revert will revert the frame or object (or the selected set) to the frame or object's default language.
• The default text styles' Base group language is inherited from the interface language. There is no connection between the default frame text and art text spelling languages and the default text styles' Base group language. You can change the default text styles' language by editing the styles and then choosing Save Styles as Default from the panel menu.
• The Base style group in your document inherits its spelling language (and everything else) from your default text styles.
• No Style isn't an actual style, it just removes the applied style and displays No Style as an indicator that you haven't chosen a style. You can't edit it because there's nothing to edit. When you apply No Style, the text reverts to the text frame or art text object's defaults. You can see this by choosing Italian and creating a frame. Type three paragraphs and change them to French. Select all three paragraphs and apply Base to them (assuming Base is Finnish for you) and they will be Finnish. Select the middle paragraph and choose Edit > Default > Revert - that paragraph will now be Italian, the text frame's default.

It's even more complicated for somebody who must publish bilingual documents. For example, imagine if you needed to format Finnish and Swedish text and you had successfully changed your frame text, art text, and text style defaults to Finnish. You create a document and draw a text frame and it will default to Finnish. You type some text and then create a second text frame, choose Swedish, and type some text. Then you edit the Finnish text some more and save and close the document.

The next day you open the document and the cursor is in the Finnish frame where you left off. In most applications, if you create a frame now it would be Finnish because that is the app default and also that's where the cursor is. But in Affinity, the new frame will be Swedish because the last time you chose a language in this document that's what you chose. There's no indication in the application interface that the language for the new frame will be different than the language shown in the Character panel. Then you create a new art text object and it's Finnish because Publisher has separate defaults for frame text and art text.

I think this is why there's a button in the Toolbar for Edit > Defaults > Revert - it's a feature that needs to be used very frequently.