Jump to content
thirty bees forum
  • 0

Localization Pack German (de)


Question

Posted

~~Complete Translation Files for German Version available for Download.~~

Translations deleted. Original Translator (copyright holder) doesn't want parts of his translations to be used by thirtybees.

Recommended Posts

  • 0
Posted

str_replace('Sie', 'Du', $string); FTW!

No, just joking. "Geben Sie hier Ihre bevorzugte Farbe an" -> "Geben Du hier Deine bevorzugte Farbe an". Sounds like a parody on our citizens with Turkish ancestry.

  • 0
Posted

Differences are interesting. In Sweden it is totally opposite. All can be spoken to using DU. But it is the same with titles. In Sweden no one is really interested in them, but in Germany they are extremely important

  • 0
Posted

I@mdekker said in Localization Pack German (de):

I think it’s a question of style. IKEA only used informal speech in Germany, and people love it. Banks, on the other hand, are typically very formal. That’s why I think having two localization packs is a good idea. Let the merchant decide whether they’d like to use formal or informal speech.

I have been thinking about that as well, but the problem here is that both Crowdin and thirty bees use one language code per language. There is no language code for the informal version, so hard to keep track of it, unless we start another Crowdin project, but that is just way too much to handle at the moment. Both too much for us and contributors.

Not really because PrestaShop introduced 3 other "languages" to Crowdin (German Austria, German Luxembourg, German Switzerland). Nonsense in my view. Anyway, there was this guy with the nickname Papapillon who wanted to translate the average 5% differences for Switzerland, therefor we uploaded the then completed 86% German for PrestaShop 1.6 into this language. When we made him proofreader he may have realized that this would be much work for him and vanished from one day to another. From this day on this translation ( included in TB too) remained nearly untouched and is now outdated. But this implies there is already a language code. This could be renamed and used for a "Du"-Version of German. But ... it would cause much work, because Traumflug is right, you have to change the grammar in thousands of items. We discussed this in the German PS Forum. There is a topic in the PrestaShop forum where I published the estimated quantities of Items to be changed.

If Michael would be so kind to upload the current translation into this language, I would post a tutorial how to use Crowdin's advanced features to minimize the efforts for the required changes for those who want to deal with this. I mean, given Crowdin will be properly configured. Currently it is not even possible to search and replace the word "Sie", because you get the notification that no matching strings were found.

  • 0
Posted

I would love to make some amendments to the German language pack (for example: Employees is translated as "Benutzerrechte" which means "user rights"). The same wrong translations shows up in prestashop. I know I can change it in my own backend but it might be confusing for newbies who are looking for the employees and don't find the menu item. Where can I make some suggestions for a better translation?

  • 0
Posted

@marci123 said in Localization Pack German (de):

I would love to make some amendments to the German language pack (for example: Employees is translated as "Benutzerrechte" which means "user rights"). The same wrong translations shows up in prestashop. I know I can change it in my own backend but it might be confusing for newbies who are looking for the employees and don't find the menu item. Where can I make some suggestions for a better translation?

98% of the current TB English source is genuine PrestaShop, unfortunately a in some parts outdated translation ( we're working on improvements). But currently (minimum since 3 month) the menu item employees is translated as Mitarbeiter, which is correct.

Du hast leider wohl schon eine Weile die Sprache nicht mehr aktualisiert, denn die "Benutzerrechte" gibt es weder in Prestashop noch in thirty bees mehr. Das war ein kurzzeitiger Fehler, den ich zu verantworten hatte, ist aber schon gut ein halbes Jahr her. Das hing mit Prestashop 1.7 zusammen, wo sich die Menüstruktur geändert hatte. Kann sein, dass thirty bees in der ersten Version auf einen veralteten Sprachbestand aus dem Crowdin-Archiv zurückgegriffen hat. Wenn du bei Crowdin mitmachen willst, solltest du dir aber darüber im Klaren sein, dass ein Großteil des Sourcecodes von Leuten verfasst wurde, die das Englische nicht sonderlich gut beherrschten. Du solltest also die Fehler, Ungereimtheiten, sprachlichen Missgriffe und irreführenden Begriffe immer erst im jeweiligen Kontext prüfen, bevor du sie übersetzt.

  • 0
Posted

98% of the current TB English source is genuine PrestaShop, unfortunately a in some parts outdated translation ( we're working on improvements). But currently (minimum since 3 month) the menu item employees is translated as Mitarbeiter, which is correct.

Yes I saw this on crowdin :-), in my thritybees install there was still the old language file.

I did some tests with the former thirty bees version to see if the beesblog module would work with the former version. This could be the reason why my language file is not up to date.

  • 0
Posted

Funny language mix, eh? As this is an english section of the forum, let me translate the last paragraph:

If you want to participate at Crowdin, you should recognize that most of the source code was written by people being not exactly excellent in English. You should review any errors, misalignments, mistakes and misleading words in their context before translating them.

My answer: looking at the context is always a good idea, no matter how well code writers know English. Because many words have different meanings depending on this context, in any language. And often this context helps a lot to find better sentences than just direct translations. German can be very elegant when not translating words, but meanings.

  • 0
Posted

Crowdin can assist the user to find the context, given the translation section is well configured. )Ok, I know where to find it, but I have the advantage that I'm dealing with this translation for years.) There is still need for some improvement to help newbies to easier grasp the context. Crowdin provides some sophisticated variables, but the admin has to use them.

  • 0
Posted

Since Employees has already been translated correctly I have made a suggestion to change "Standardsprache im Backoffice verwenden" to "Mitgliedern die Auswahl einer Sprache erlauben" because I think "Standardsprache verwenden" can be misleading since it sounds as if it is "one language for all" if it is changed. The original is "allow employees to select a specific language for the admin panel" says that each user may change their language. I think "use default language?" doesn't sound as if each user may change their language. Just my 2 cents ...

  • 0
Posted

Though it is quite common I hate this term Standardsprache. And in this special case you are right, the current translation is misleading. I did not follow exactly your proposal and btw changed not only the hint, but the field item too. Hope this is OK for you:

Memorize the language used in Admin panel forms --> Spracheinstellung des Back Office merken Allow employees to select a specific language for the Admin panel form. --> Mitarbeiter dürfen eine andere Sprache für das Back Office wählen.

Anyway, the source text is ... worthy of improvement.

  • 0
Posted

I'm not sure if all modules are really up to date. I checked some of them already but currently my leisure time is limited. And there is a lot of translations (concerning PS Addons e.g.) that were ok for PS but are currently wrong or unnecessary for thirty bees.

  • 0
Posted

I made some revisions in comparison to the original PrestaShop translation. The German localization pack is now completed und 100% approved. :) Hope it will be available soon - in any case you can download it directly from Crowdin. Please test it and give us a feedback, if there's still something wrong or in need of improvement.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...