25.0: fix order of FirstName and LastName for suite
authorDaiki Noda <demonnroki3150@gmail.com>
Fri, 23 Aug 2013 00:12:03 +0900
changeset 1000 032371bef829dcf51e2f79663efeafeb226c8361
parent 999 8446673a2dcfe48f3df1c3f5c908ea335b927592
child 1001 f5bc8f8e0ab6d5abd36488d7a9a1eecfd826faa1
push id436
push userzbraniecki@mozilla.com
push dateMon, 16 Sep 2013 19:44:30 +0000
bugs25
25.0: fix order of FirstName and LastName for suite
suite/chrome/mailnews/addressbook/abCardOverlay.dtd
--- a/suite/chrome/mailnews/addressbook/abCardOverlay.dtd
+++ b/suite/chrome/mailnews/addressbook/abCardOverlay.dtd
@@ -10,23 +10,23 @@
  NameField1, NameField2, PhoneticField1, PhoneticField2
  those fields are either LN or FN depends on the target country.
  "FirstName" and "LastName" can be swapped for id to change the order
  but they should not be translated (same applied to phonetic id).
  Make sure the translation of label corresponds to the order of id.
 -->
 
 <!-- LOCALIZATION NOTE (NameField1.id) : DONT_TRANSLATE -->
-<!ENTITY NameField1.id                  "FirstName">
+<!ENTITY NameField1.id                  "LastName">
 <!-- LOCALIZATION NOTE (NameField2.id) : DONT_TRANSLATE -->
-<!ENTITY NameField2.id                  "LastName">
+<!ENTITY NameField2.id                  "FirstName">
 <!-- LOCALIZATION NOTE (PhoneticField1.id) : DONT_TRANSLATE -->
-<!ENTITY PhoneticField1.id              "PhoneticFirstName">
+<!ENTITY PhoneticField1.id              "PhoneticLastName">
 <!-- LOCALIZATION NOTE (PhoneticField2.id) : DONT_TRANSLATE -->
-<!ENTITY PhoneticField2.id              "PhoneticLastName">
+<!ENTITY PhoneticField2.id              "PhoneticFirstName">
 
 <!ENTITY NameField1.label               "姓:">
 <!ENTITY NameField1.accesskey           "F">
 <!ENTITY NameField2.label               "名:">
 <!ENTITY NameField2.accesskey           "L">
 <!ENTITY PhoneticField1.label           "よみがな:">
 <!ENTITY PhoneticField2.label           "よみがな:">
 <!ENTITY DisplayName.label              "表示名:">