Patch #4870

Correct two german localisation problems

Added by Lukas Elmer almost 8 years ago. Updated over 7 years ago.

Status:ClosedStart date:2010-02-18
Priority:NormalDue date:2010-02-21
Assignee:Azamat Hackimov% Done:

0%

Category:Translations
Target version:-

Description

This patch updates the German locale.

de.yml.patch Magnifier (661 Bytes) Lukas Elmer, 2010-02-18 01:33

de.yml Magnifier - de.yml (39.6 KB) Thomas Löber, 2010-02-18 17:51

de.yml.only-for-demonstration.diff Magnifier - Sorted old/new (only to show the differences) (10.6 KB) Thomas Löber, 2010-02-19 13:22


Related issues

Duplicated by Redmine - Patch #4847: German translations Closed 2010-02-15

Associated revisions

Revision 3470
Added by Azamat Hackimov almost 8 years ago

Translation updates

History

#1 Updated by Thomas Löber almost 8 years ago

Hi!

This week I had the time to make a new version of de.yml suitable for trunk and 0.9-stable.

Changes:

  • fixed typos, punctuation etc.
  • changed some terms so they are consistent with the existing terms
  • changed the default time format to "%d.%m.%Y %H:%M"
  • regarding the translation from this issue: I already translated it to "Anlegen + nächstes Ticket". I hope this is OK for Lukas!
  • added the translations from #4847
  • reordered the lines so they are the same as in en.yml

I'm attaching the complete file because a diff doesn't make sense due to the reordering.

Any suggestions for improvements are welcome!

#2 Updated by Felix Schäfer almost 8 years ago

Pitty, I would have liked to see a diff :-) Could you maybe make a diff of the sorted files, so that I can check what changed? Thanks.

#3 Updated by Thomas Löber almost 8 years ago

Sure. It was a little bit complicated to make a diff which only shows which lines changed (and not which lines have been moved around).

I had to read the old and the new de.yml file and output a sorted YAML version of each one:

#
# http://snippets.dzone.com/posts/show/5811
#
class Hash
  # Replacing the to_yaml function so it'll serialize hashes sorted (by their keys)
  #
  # Original function is in /usr/lib/ruby/1.8/yaml/rubytypes.rb
  def to_yaml( opts = {} )
    YAML::quick_emit( object_id, opts ) do |out|
      out.map( taguri, to_yaml_style ) do |map|
        sort.each do |k, v|   # <-- here's my addition (the 'sort')
          map.add( k, v )
        end
      end
    end
  end
end

puts YAML.load(File.open(ARGV[0])).to_yaml

Finally these alphabetically sorted files could be diffed. I'm attaching the result as de.yml.only-for-demonstration.diff.

#4 Updated by Felix Schäfer almost 8 years ago

Ok, my thought was to use the sort command on your favorite POSIX compliant shell/OS on both files and compare them, that should have done the trick ^_^

Anyway, the changes look good, +1 :-)

#5 Updated by Azamat Hackimov almost 8 years ago

  • Due date set to 2010-02-21
  • Status changed from New to Closed
  • Target version set to 0.9.3

Commited to svn, thank you.

#6 Updated by Jens Goldhammer almost 8 years ago

  • Status changed from Closed to Reopened

Very good corrections. But I think, we should be aware of the user of hyphens.
In German hyphens are used to avoid misunderstandings or to emphasise unknown word parts in new word creations.

Look at http://www.spiegel.de/kultur/zwiebelfisch/0,1518,274613,00.html for more information.

Grundsätzlich gilt: Ein Bindestrich ist immer dort willkommen, wo es gilt, ein Missverständnis zu vermeiden oder einen Bestandteil hervorzuheben; er dient also dem Ziel, Klarheit zu schaffen.

So in my eyes, Ticketstatus is better to read than Ticket-Status.
That is my opinion. What do others think?

#7 Updated by Jean-Philippe Lang almost 8 years ago

  • Target version deleted (0.9.3)

#8 Updated by Thomas Löber almost 8 years ago

Jens Goldhammer wrote:

So in my eyes, Ticketstatus is better to read than Ticket-Status.
That is my opinion. What do others think?

That fine with me as long as it is consistent throughout the file.

Here is a list of all the hyphenated words in de.yml. Which other terms (besides Ticket-*) should be written as one word?

Administrator-Kennwort
API-Schlüssel
API-Zugriffsschlüssel
Applikations-Titel
Applikations-Untertitel
Atom-Feed
Atom-Zugriffsschlüssel
Authentifizierungs-Arten
Authentifizierungs-Modus
Authentifizierungs-Quelle
Benutzer-Anzeigeformat
Commit-Log-Meldungen
Commit-Zugriff
CSV/PDF-Export
Default-Spalten
Default-Sprache
Diff-Zeilen
E-Mail-Absender
E-Mail-Adresse
E-Mail-Adressen
E-Mail-Attribut
E-Mail-Fußzeile
Gantt-Diagramm
Gravatar-Benutzerbilder
Kategorie-Zuordnung
Konto-Informationen
LDAP-Authentifizierung
Mitgliedsname-Attribut
Name-Attribut
Nicht-Administrator
On-the-fly-Benutzererstellung
OpenID-Anmeldung
OpenID-URL
Plugin-Assets
Projekt-Aktivität
Projektarchiv-Benutzernamen
Projekt-Homepage
Quell-Rolle
Quell-Tracker
Redmine-Benutzer
REST-Schnittstelle
RSS-Zugriffsschlüssel
SMTP-Server
Standard-Gravatar-Bild
Standard-Konfiguration
Standard-Spalten
System-Aktivität
Test-E-Mail
Ticket-Auflistung
Ticket-Beziehungen
Ticket-Feld
Ticket-Fortschritt
Ticket-Kategorie
Ticket-Kategorien
Ticket-Prioritäten
Ticket-Status
Ticket-Verfolgung
Vorname-Attribut
Wiki-Bearbeitung
Wiki-Bearbeitungen
Wiki-Historie
Wiki-Seite
Wiki-Seiten
Wiki-Versionsgeschichte
Ziel-Tracker

#9 Updated by Felix Schäfer over 7 years ago

What's the current status on this?

#10 Updated by Azamat Hackimov over 7 years ago

  • Status changed from Reopened to Closed

Also available in: Atom PDF