Plain language improvements to messages in the language file

[Ildest]

Description

I pitched this idea to @framitdavid a while ago, as an improvement task with some quick wins, to do over the summer.

The idea is to go through and edit he language file, in particular messages to the end user, and improve

• wording/sentece structure
• plain language

Example:

"Aktørlisten vil bli filtrert i Altinn Studio preview basert på aktørkrav."

"I forhåndsvisningen filtreres aktørlisten ut fra aktørkravene."

(Not taking into account that we might change the word "aktør" at some point, just an example of plain language revision).

Some strings may need context to be interpreted correctly, and I will be careful not to revise strings that I am unsure of. Some strings may also be difficult to change because we have not decided on the correct terms yet.

This work can be done in two ways, as I see it:

1. I can edit the original file and put comments on lines where I need context, so that one of you guys can help with that before I make a pull request at the end.
2. We can make a copy of the file, and I can fearlessly play with that and put comments where I need context. That requires one of you to revise thoroughly and make the pull request/merge.

Any other ideas and suggestions are welcome :-). Shout out if you see problems with the issue.

Why should we do dhis?

To give our end-users better messages/Studio texts in a short time(as a quick fix). It is a good time to do it, over the summer.

Additional Information

I have revised strings in large software/apps many times before, for example in Visma Autopay, which contained up to 10 000 strings of text.

Tasks

• [ ] Review language.md file (not sure I have the file name correct here yet)
• [ ] Get it done

Acceptance Criterias

Peer review before pull reqeust

[Ildest]

Is there a way to mark strings that have NOT been edited?

[Ildest]

2000+ strenger Note texts that are similar and make them similar