If you can, please run make fix-all

Thanks @beerisgood 👍🏻
If you can, try to make all the changes as part of the same patch. But otherwise no worry, keep going and I will but them back together here

Thanks @beerisgood 👍🏻 If you can, try to make all the changes as part of the same patch. But otherwise no worry, keep going and I will but them back together here

sorry I didnt't read your answer here before. Now I'm finished

Thanks, 100% 👍🏻

@Alkarex

Sorry, I overlooked the open request and had a long day.

German is a very flexible language, but that also makes it complex.

Let me start from the end.

What do you want the software to focus on?

• Formal
• Everyday language
• Technical
• Simple language

I would recommend one type of translation or the other depending on the context.

In the case of Icon, for example, both Icon and Symbol are possible. The latter would be a classic, purely German translation. Technically correct.

Icon would be an everyday variant that we now use in everyday life. Due to the strong influence of English in our everyday lives. Especially among younger people. :)

@Anagastes I would go for Everyday language for common features, while advanced features should likely be Technical (as opposed to try to reformulate them in simple language). But it also strongly depends on the availability of people helping maintaining the translation and their own preference. I will mostly try to make sure we are not embarking on any edit war :-P

Okay, I'll delete my request and start again. With the desired aspects.

But it will take longer, because I first have to see what would be in the ‘user’ area and what would be more of an admin part.

After that, you can decide for yourselves whether you like it or not :D

The target user of FreshRSS are people who aren't beginner in using software. They often host the software themself. Minimum they know where to find a RSS/Atom link (sometime they are hidden) and paste it into the software. They are more experienced then a default Facebook/Instagram user ;)

@beerisgood How can we help to finish this very useful PR?

@beerisgood How can we help to finish this very useful PR?

Isn’t the PR already merged?

No it's the other one that got closed (and unmerged): #7844

It would be nice to get this PR competed in time for 1.27.1, which is almost ready

It would be nice to get this PR competed in time for 1.27.1, which is almost ready

I’m fine with the posted suggestions for some strings. Can this be merged or is any further work needed?

It would be nice to get this PR competed in time for 1.27.1, which is almost ready

I’m fine with the posted suggestions for some strings. Can this be merged or is any further work needed?

There are suggestions made by @math-GH that need to be either dismissed or merged.

@Anagastes Now that this PR is merged, you are much welcome to resume your work in a new PR