Check the proofing language before changing approved Norwegian copy

An editor marks a word as wrong. The reviewer accepts its suggestion, and a page that was approved in Nynorsk begins to acquire Bokmål wording. Nothing failed in the export or the website's character encoding. The review used a different language resource from the one the document needed.

That is a practical content-adaptation problem for a Norway-connected organisation. A language choice must reach the people and tools that prepare the wording, not merely the language switch on a finished website. This guide follows a fictional service publisher through one such review and separates dictionary configuration from approval of the finished message.

Establish what the source actually says

The publisher has two independently approved information sheets. Document N-24 is Nynorsk; document B-16 is Bokmål. Both explain how to make an enquiry, but they have separate revision histories and reviewers. N-24 uses førespurnad in its approved heading. B-16 uses forespørsel. The official Ordbøkene entries identify those forms in their respective dictionaries.

The reviewer first checks the agreed language and approved revision of N-24. They do not infer Nynorsk from the organisation's address or assume every Norwegian reader wants the same written standard. The project record says that this particular sheet is to remain Nynorsk and names the person who can approve changes.

A proofing warning is therefore evidence to investigate. It is not, on its own, permission to replace an approved word.

Inspect the document's effective settings

In the fictional installed editor, both relevant dictionaries are available and a document can select its proofing language. The team confirms that capability in the actual installation. N-24 was created from a template whose effective proofing setting is Norwegian Bokmål. Its visible Nynorsk language label is merely a note written at the top of the document; it does not control the checker.

The editor flags førespurnad and offers forespørsel. The source text has not changed yet. The reviewer records the warning and the selected dictionary before accepting any replacement. This preserves the distinction between what the approved document contains and what the tool recommends.

LibreOffice's language guidance provides a real example of language settings determining proofing dictionaries. The exact menus, installed dictionaries and effects on selected text must be checked in the editor being used. A menu labelled Norwegian does not establish that a Nynorsk dictionary is present and active.

Make the smallest appropriate correction

The publisher selects the installed Nynorsk proofing profile for N-24's intended text. It leaves the approved heading unchanged. The team also inspects any text with its own language assignment so that a document-level choice does not conceal a differently configured passage.

This is not a request to ignore all warnings, add every flagged term to a private dictionary or turn checking off. Those shortcuts can make the visible problem disappear while disabling the assistance the reviewer still needs. Nor is it a global change to every open document. B-16 has a legitimate Bokmål review requirement.

The reviewer then saves and reopens N-24 in the supported workflow. The effective setting remains Nynorsk. The same heading is checked again, and the warning caused by the mismatched dictionary is gone in this inspected setup. The approved source and saved output still contain førespurnad.

Keep a real error in the exercise

A useful test must show that proofing still does something. The team makes a separate test copy containing førespurnadd, an intentional extra-letter error. In the fictional configured checker, that test word is flagged. The reviewer corrects the test copy back to the approved form and checks it again. The intentional error is never introduced into the approved publication source.

The table describes this fictional installation's observed acceptance exercise. It does not promise identical suggestions from every dictionary version, editor or language extension.

Decide what a clean result does not settle

A dictionary can recognise a word without understanding whether the instruction is true, polite, complete or suitable for its audience. The publisher's language reviewer still reads the whole sheet. They check the customer action, the organisation's terminology and any limitations on the service. A technical reviewer separately follows the enquiry link and checks that its destination fulfils the stated purpose.

If the approved instruction changes, both the Nynorsk and Bokmål owners need to consider the change. That is a content decision with its own record; a spelling setting cannot keep two independently edited documents equivalent. The project should also identify who handles later editorial questions and whether translated material is included in the support arrangement.

For this publisher, the completed result is narrow and useful: N-24 keeps its approved Nynorsk wording, its supported checker uses the intended dictionary, a deliberate mistake remains detectable, and B-16 retains its separate Bokmål treatment. The release reviewer can see both the language decision and the evidence that the tooling respects it.

Bring one approved document, the warning that prompted a proposed change and the editor's effective language settings to a project discussion. That is enough to investigate the boundary before changing a whole collection of Norwegian content.