chrome/app/address_input_strings.grdp - Issue 304223010: Include upstream libaddressinput strings in Chrome build.

Side by Side Diff: chrome/app/address_input_strings.grdp

Issue 304223010: Include upstream libaddressinput strings in Chrome build. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Created 6 years, 6 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

OLD	NEW
(Empty)
	1 <?xml version="1.0" encoding="utf-8"?>

	2 <!--

	3 Copyright (C) 2013 Google Inc.

	4

	5 Licensed under the Apache License, Version 2.0 (the "License");

	6 you may not use this file except in compliance with the License.

	7 You may obtain a copy of the License at

	8

	9 http://www.apache.org/licenses/LICENSE-2.0

	10

	11 Unless required by applicable law or agreed to in writing, software

	12 distributed under the License is distributed on an "AS IS" BASIS,

	13 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

	14 See the License for the specific language governing permissions and

	15 limitations under the License.

	16

	17 This file is a copy of third_party/libaddressinput/src/cpp/res/messages.grdp

	18 that's been relocated and renamed to work better with translation tools.

	19 -->

	20 <grit-part>

	21 <message

	22 name="IDS_LIBADDRESSINPUT_COUNTRY_OR_REGION_LABEL"

	23 desc="A country or a political region (Countries like the United States or
	Lei Zhang 2014/05/31 01:39:48 80 column rules don't seem to apply in grd files 80 column rules don't seem to apply in grd files please use gerrit instead 2014/06/01 14:27:27 Good observation :-). That's because GRD text mess Show quoted text On 2014/05/31 01:39:48, Lei Zhang wrote: > 80 column rules don't seem to apply in grd files Good observation :-). That's because GRD text messages are parsed as literal strings where each newline or space (except trailing and leading) are present in the resulting string. Thus we're forced to have super long lines for the text messages. However, nothing (as far as I know) prevents us from having nicely readable description messages. I find these to be easier to parse for a human... Would you agree? On possibility is that the translation tools might be sensitive to the newlines and whitespace in the description. If that's the case, then I would have to undo my hard work to make the descriptions readable. :-\ Lei Zhang 2014/06/02 20:47:43 All the other .grd files in this directory do not Show quoted text On 2014/06/01 14:27:27, Rouslan Solomakhin wrote: > On 2014/05/31 01:39:48, Lei Zhang wrote: > > 80 column rules don't seem to apply in grd files > > Good observation :-). That's because GRD text messages are parsed as literal > strings where each newline or space (except trailing and leading) are present in > the resulting string. Thus we're forced to have super long lines for the text > messages. However, nothing (as far as I know) prevents us from having nicely > readable description messages. I find these to be easier to parse for a human... > Would you agree? > > On possibility is that the translation tools might be sensitive to the newlines > and whitespace in the description. If that's the case, then I would have to undo > my hard work to make the descriptions readable. :-\ All the other .grd files in this directory do not wrap at 80 chars. So it's better to match the existing convention. please use gerrit instead 2014/06/02 21:07:21 Done. Show quoted text On 2014/06/02 20:47:43, Lei Zhang wrote: > On 2014/06/01 14:27:27, Rouslan Solomakhin wrote: > > On 2014/05/31 01:39:48, Lei Zhang wrote: > > > 80 column rules don't seem to apply in grd files > > > > Good observation :-). That's because GRD text messages are parsed as literal > > strings where each newline or space (except trailing and leading) are present > in > > the resulting string. Thus we're forced to have super long lines for the text > > messages. However, nothing (as far as I know) prevents us from having nicely > > readable description messages. I find these to be easier to parse for a > human... > > Would you agree? > > > > On possibility is that the translation tools might be sensitive to the > newlines > > and whitespace in the description. If that's the case, then I would have to > undo > > my hard work to make the descriptions readable. :-\ > > All the other .grd files in this directory do not wrap at 80 chars. So it's > better to match the existing convention. Done.
	24 regions like Hong Kong or Macao, or places like Taiwan, where

	25 whether it is a country or not is a politically sensitive

	26 question).">

	27 Country / Region

	28 </message>

	29 <message

	30 name="IDS_LIBADDRESSINPUT_LOCALITY_LABEL"

	31 desc="E.g., New York City.">

	32 City

	33 </message>

	34 <message

	35 name="IDS_LIBADDRESSINPUT_ADDRESS_LINE_1_LABEL"

	36 desc="E.g., 18th Street, Unit 3.">

	37 Street address

	38 </message>

	39 <message

	40 name="IDS_LIBADDRESSINPUT_POSTAL_CODE_LABEL"

	41 desc="Postal Code. Values are frequently alphanumeric. Used in countries

	42 such as Switzerland.">

	43 Postal code

	44 </message>

	45 <message

	46 name="IDS_LIBADDRESSINPUT_ZIP_CODE_LABEL"

	47 desc="ZIP code. Values are frequently alphanumeric. Used in countries such

	48 as the US.">

	49 ZIP code

	50 </message>

	51 <message

	52 name="IDS_LIBADDRESSINPUT_AREA"

	53 desc="Administrative Area for Hong Kong (e.g., Kowloon).">

	54 Area

	55 </message>

	56 <message

	57 name="IDS_LIBADDRESSINPUT_COUNTY"

	58 desc="Administrative Area for United Kingdoms (e.g. York) or for the

	59 United States (e.g. Orange County).">

	60 County

	61 </message>

	62 <message

	63 name="IDS_LIBADDRESSINPUT_DEPARTMENT"

	64 desc="Administrative Area for Nicaragua (e.g., Boaco) or France.">

	65 Department

	66 </message>

	67 <message

	68 name="IDS_LIBADDRESSINPUT_DISTRICT"

	69 desc="Administrative Area for Nauru Central Pacific (e.g., Aiwo district),

	70 or area of a town (a neighbourhood/suburb) used for addresses in

	71 Korea and China.">

	72 District

	73 </message>

	74 <message

	75 name="IDS_LIBADDRESSINPUT_DO_SI"

	76 desc="Administrative Area for Korea (e.g., Gyeonggi-do or Busan-si).">

	77 Do/Si

	78 </message>

	79 <message

	80 name="IDS_LIBADDRESSINPUT_EMIRATE"

	81 desc="Administrative Area for United Arab Emirates (e.g., Abu Dhabi).">

	82 Emirate

	83 </message>

	84 <message

	85 name="IDS_LIBADDRESSINPUT_ISLAND"

	86 desc="Administrative Area for certain countries (e.g., Bahama's Cat

	87 Island).">

	88 Island

	89 </message>

	90 <message

	91 name="IDS_LIBADDRESSINPUT_PARISH"

	92 desc="Administrative Area for certain countries (e.g., Andorra's

	93 Canillo).">

	94 Parish

	95 </message>

	96 <message

	97 name="IDS_LIBADDRESSINPUT_PREFECTURE"

	98 desc="Administrative Area for Japan (e.g., Hokkaido).">

	99 Prefecture

	100 </message>

	101 <message

	102 name="IDS_LIBADDRESSINPUT_PROVINCE"

	103 desc="Administrative Area for certain countries (e.g., France's

	104 Champagne).">

	105 Province

	106 </message>

	107 <message

	108 name="IDS_LIBADDRESSINPUT_STATE"

	109 desc="Administrative Area for certain countries (e.g., US' California).">

	110 State

	111 </message>

	112 <message

	113 name="IDS_LIBADDRESSINPUT_RECIPIENT_LABEL"

	114 desc="Label for the field for a person's name in an address.">

	115 Name

	116 </message>

	117 <message

	118 name="IDS_LIBADDRESSINPUT_MISSING_REQUIRED_FIELD"

	119 desc="Error message shown with a UI field when it is a required field and

	120 the user has not filled it out.">

	121 You can't leave this empty.

	122 </message>

	123 <message

	124 name="IDS_LIBADDRESSINPUT_MISSING_REQUIRED_POSTAL_CODE_EXAMPLE_AND_URL"

	125 desc="Error message shown with the postal code field when it is a required

	126 field and the user has not filled it out, providing an example

	127 postal code and a link to this country's postal service that a user

	128 can use to look up their postal code.">

	129 You must provide a postal code, for example <ph name="EXAMPLE">$1<ex>90291</ ex></ph>. Don't know your postal code? Find it out <ph name="BEGIN_LINK">$2</ph> here<ph name="END_LINK">$3</ph>.

	130 </message>

	131 <message

	132 name="IDS_LIBADDRESSINPUT_MISSING_REQUIRED_POSTAL_CODE_EXAMPLE"

	133 desc="Error message shown with the postal code field when it is a required

	134 field and the user has not filled it out, providing an example

	135 postal code.">

	136 You must provide a postal code, for example <ph name="EXAMPLE">$1<ex>90291</ ex></ph>.

	137 </message>

	138 <message

	139 name="IDS_LIBADDRESSINPUT_MISSING_REQUIRED_ZIP_CODE_EXAMPLE_AND_URL"

	140 desc="Error message shown with the ZIP code field when it is a required

	141 field and the user has not filled it out, providing an example ZIP

	142 code and a link to this country's postal service that a user can use

	143 to look up their ZIP code. This is specifically for countries using

	144 ZIP codes instead of Postal codes, such as America.">

	145 You must provide a ZIP code, for example <ph name="EXAMPLE">$1<ex>90291</ex> </ph>. Don't know your ZIP code? Find it out <ph name="BEGIN_LINK">$2</ph>here<p h name="END_LINK">$3</ph>.

	146 </message>

	147 <message

	148 name="IDS_LIBADDRESSINPUT_MISSING_REQUIRED_ZIP_CODE_EXAMPLE"

	149 desc="Error message shown with the ZIP code field when it is a required

	150 field and the user has not filled it out, providing an example ZIP

	151 code.">

	152 You must provide a ZIP code, for example <ph name="EXAMPLE">$1<ex>90291</ex> </ph>.

	153 </message>

	154 <message

	155 name="IDS_LIBADDRESSINPUT_UNKNOWN_VALUE"

	156 desc="Occurs when the user fills out the wrong value for an address field.

	157 For example, this would be shown when putting 'Cupertino' in United

	158 States' State field.">

	159 <ph name="FIELD_VALUE">$1<ex>Cupertino</ex></ph> is not recognized as a know n value for this field.

	160 </message>

	161 <message

	162 name="IDS_LIBADDRESSINPUT_UNRECOGNIZED_FORMAT_POSTAL_CODE_EXAMPLE_AND_URL"

	163 desc="Occurs when the user fills out a postal code that does not conform

	164 to the country's postal code format. For example, this would be

	165 shown when using '80' as a Swiss postal code, which is normally 4

	166 digits long. Provides an example postal code and a link to this

	167 country's postal service that a user can use to look up their postal

	168 code.">

	169 This postal code format is not recognized. Example of a valid postal code: < ph name="EXAMPLE">$1<ex>90291</ex></ph>. Don't know your postal code? Find it ou t <ph name="BEGIN_LINK">$2</ph>here<ph name="END_LINK">$3</ph>.

	170 </message>

	171 <message

	172 name="IDS_LIBADDRESSINPUT_UNRECOGNIZED_FORMAT_POSTAL_CODE_EXAMPLE"

	173 desc="Occurs when the user fills out a postal code that does not conform

	174 to the country's postal code format. For example, this would be

	175 shown when using '80' as a Swiss postal code, which is normally 4

	176 digits long. Provides an example postal code.">

	177 This postal code format is not recognized. Example of a valid postal code: < ph name="EXAMPLE">$1<ex>90291</ex></ph>.

	178 </message>

	179 <message

	180 name="IDS_LIBADDRESSINPUT_UNRECOGNIZED_FORMAT_POSTAL_CODE"

	181 desc="Occurs when the user fills out a postal code that does not conform

	182 to the country's postal code format. For example, this would be

	183 shown when using '80' as a Swiss postal code, which is normally 4

	184 digits long.">

	185 This postal code format is not recognized.

	186 </message>

	187 <message

	188 name="IDS_LIBADDRESSINPUT_UNRECOGNIZED_FORMAT_ZIP_CODE_EXAMPLE_AND_URL"

	189 desc="Occurs when the user fills out a ZIP code that does not conform to

	190 the country's ZIP code format. For example, this would be shown when

	191 using '901' as a ZIP code for the United States. Provides an example

	192 ZIP code and a link to this country's postal service that a user can

	193 use to look up their ZIP code.">

	194 This ZIP code format is not recognized. Example of a valid ZIP code: <ph nam e="EXAMPLE">$1<ex>90291</ex></ph>. Don't know your ZIP code? Find it out <ph nam e="BEGIN_LINK">$2</ph>here<ph name="END_LINK">$3</ph>.
	Lei Zhang 2014/05/31 01:39:48 "find it out" -> "find out" ? It's up to you and "find it out" -> "find out" ? It's up to you and Evan to agree on the messages here. please use gerrit instead 2014/06/01 14:27:27 Nope, it's not up to me and Evan, because we have Show quoted text On 2014/05/31 01:39:48, Lei Zhang wrote: > "find it out" -> "find out" ? > > It's up to you and Evan to agree on the messages here. Nope, it's not up to me and Evan, because we have translations for these strings ;-). Changing these strings will cause a translation request, which must be curated by the i18n team, because these strings are tricky to get right in most languages. For example, a novice translator might translate CEDEX, postal code, and ZIP code into a single phrase "postal code", but that would not be correct. So we're trying to avoid any additional translation effort by re-using these existing strings with translations. Lei Zhang 2014/06/02 20:47:43 SGTM. Show quoted text On 2014/06/01 14:27:27, Rouslan Solomakhin wrote: > On 2014/05/31 01:39:48, Lei Zhang wrote: > > "find it out" -> "find out" ? > > > > It's up to you and Evan to agree on the messages here. > > Nope, it's not up to me and Evan, because we have translations for these strings > ;-). Changing these strings will cause a translation request, which must be > curated by the i18n team, because these strings are tricky to get right in most > languages. For example, a novice translator might translate CEDEX, postal code, > and ZIP code into a single phrase "postal code", but that would not be correct. > So we're trying to avoid any additional translation effort by re-using these > existing strings with translations. SGTM.
	195 </message>

	196 <message

	197 name="IDS_LIBADDRESSINPUT_UNRECOGNIZED_FORMAT_ZIP_CODE_EXAMPLE"

	198 desc="Occurs when the user fills out a ZIP code that does not conform to

	199 the country's ZIP code format. For example, this would be shown when

	200 using '901' as a ZIP code for the United States. Provides an example

	201 ZIP code.">

	202 This ZIP code format is not recognized. Example of a valid ZIP code: <ph nam e="EXAMPLE">$1<ex>90291</ex></ph>.

	203 </message>

	204 <message

	205 name="IDS_LIBADDRESSINPUT_UNRECOGNIZED_FORMAT_ZIP"

	206 desc="Occurs when the user fills out a ZIP code that does not conform to

	207 the country's ZIP code format. For example, this would be shown when

	208 using '901' as a ZIP code for the United States.">

	209 This ZIP code format is not recognized.

	210 </message>

	211 <message

	212 name="IDS_LIBADDRESSINPUT_MISMATCHING_VALUE_POSTAL_CODE_URL"

	213 desc="Occurs when the user fills out the wrong postal code for a certain

	214 location. For example, this would be shown when using Z3Z 2Y7 for

	215 Alberta, Canada. Provides a link to this country's postal service

	216 that a user can use to look up their postal code.">

	217 This postal code does not appear to match the rest of this address. Don't kn ow your postal code? Find it out <ph name="BEGIN_LINK">$1</ph>here<ph name="END_ LINK">$2</ph>.

	218 </message>

	219 <message

	220 name="IDS_LIBADDRESSINPUT_MISMATCHING_VALUE_POSTAL_CODE"

	221 desc="Occurs when the user fills out the wrong postal code for a certain

	222 location. For example, this would be shown when using Z3Z 2Y7 for

	223 Alberta, Canada.">

	224 This postal code does not appear to match the rest of this address.

	225 </message>

	226 <message

	227 name="IDS_LIBADDRESSINPUT_MISMATCHING_VALUE_ZIP_URL"

	228 desc="Occurs when the user fills out the wrong ZIP code for a certain

	229 location. For example, this would be shown when using 10001 for

	230 Arizona state. Provides a link to this country's postal service that

	231 a user can use to look up their ZIP code.">

	232 This ZIP code does not appear to match the rest of this address. Don't know your ZIP code? Find it out <ph name="BEGIN_LINK">$1</ph>here<ph name="END_LINK"> $2</ph>.

	233 </message>

	234 <message

	235 name="IDS_LIBADDRESSINPUT_MISMATCHING_VALUE_ZIP"

	236 desc="Occurs when the user fills out the wrong ZIP code for a certain

	237 location. For example, this would be shown when using 10001 for

	238 Arizona state.">

	239 This ZIP code does not appear to match the rest of this address.

	240 </message>

	241 <message

	242 name="IDS_LIBADDRESSINPUT_PO_BOX_FORBIDDEN_VALUE"

	243 desc="Occurs when the user fills out a P.O. box as part of a physical

	244 address.">

	245 This address line appears to contain a post office box. Please use a street or building address.

	246 </message>

	247 </grit-part>

OLD	NEW

« chrome/app/address_input_strings.grd ('K') | « chrome/app/address_input_strings.grd ('k') | chrome/app/resources/address_input_strings_am.xtb » ('j') | no next file with comments »