Skip to content

Commit

Permalink
Automatic translation import
Browse files Browse the repository at this point in the history 
Change-Id: I4cac0b4d8d72fd3e7dc4af3a162fee6d80575b1f
  • Loading branch information
clyde@build01 committed Dec 16, 2016
1 parent 8bc1484 commit 376b4b0
Show file tree
Hide file tree
Showing 4 changed files with 214 additions and 0 deletions.
13 changes: 13 additions & 0 deletions res/values-eo/strings.xml
View file
Expand Up @@ -38,8 +38,16 @@
part of the subject of the message that's sent) -->
<!-- Indicate when a meeting takes place. This is presented in in bullet
form, as in, "When: xxx" followed by "Where: xxx" -->
<string name="meeting_when">
Kiam:
<xliff:g id="when">%s</xliff:g>
</string>
<!-- Indicate where a meeting takes place. This is presented in in bullet
form, as in, "When: xxx" followed by "Where: xxx" -->
<string name="meeting_where">
Kie:
<xliff:g id="where">%s</xliff:g>
</string>
<!-- Indicate that a meeting is recurring. This would normally be presented
after "When: xxx", e.g. "When: Tue, Mar 10, 2010 at 2:30pm (recurring)" -->
<!-- Indicate that a meeting lasts all day. This would normally be presented
Expand Down Expand Up @@ -89,10 +97,15 @@
<!-- In account setup options & account settings screens (exchange), sync window length; this
implies loading a 'reasonable' number of messages [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<string name="account_setup_options_mail_window_1day">Unu tago</string>
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<string name="account_setup_options_mail_window_3days">Tri tagoj</string>
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<string name="account_setup_options_mail_window_1week">Unu semajno</string>
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<string name="account_setup_options_mail_window_2weeks">Du semajnoj</string>
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<string name="account_setup_options_mail_window_1month">Unu monato</string>
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- Title for notification warning about an authentication error [CHAR LIMIT=40] -->
<!-- text for notification warning about an authentication error [CHAR LIMIT=60] -->
Expand Down
100 changes: 100 additions & 0 deletions res/values-es-rCO/strings.xml
View file
@@ -0,0 +1,100 @@
<?xml version="1.0" encoding="utf-8"?>
<!--Generated by crowdin.com-->
<!-- Copyright (C) 2008 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<!-- Deprecated strings - Move the identifiers to this section, mark as
DO NOT TRANSLATE, and remove the actual text. These will be removed in a
bulk operation. -->
<!-- Do Not Translate. Unused string. -->
<!-- Short name of Microsoft Exchange account type; used by AccountManager -->
<!-- Long name of Microsoft Exchange account type; used by AccountManager -->
<!-- Message subject for meeting accepted response. This will be followed
by a colon and the title of the meeting (i.e. the title of the meeting becomes
part of the subject of the message that's sent) -->
<!-- Message subject for meeting declined response. This is followed by
a colon and the title of the meeting (i.e. the title of the meeting becomes
part of the subject of the message that's sent) -->
<!-- Message subject for meeting tentative response. This is followed by
a colon and the title of the meeting (i.e. the title of the meeting becomes
part of the subject of the message that's sent) -->
<!-- Message subject for a canceled meeting email. This is followed by a
colon and the title of the meeting (i.e. the title of the meeting becomes
part of the subject of the message that's sent) -->
<!-- Message subject for an updated meeting email. This is followed by a
colon and the title of the meeting (i.e. the title of the meeting becomes
part of the subject of the message that's sent) -->
<!-- Indicate when a meeting takes place. This is presented in in bullet
form, as in, "When: xxx" followed by "Where: xxx" -->
<!-- Indicate where a meeting takes place. This is presented in in bullet
form, as in, "When: xxx" followed by "Where: xxx" -->
<!-- Indicate that a meeting is recurring. This would normally be presented
after "When: xxx", e.g. "When: Tue, Mar 10, 2010 at 2:30pm (recurring)" -->
<!-- Indicate that a meeting lasts all day. This would normally be presented
after "When: xxx", e.g. "When: Tue, Mar 10, 2010 (all day)" -->
<!-- Indicate that a meeting lasts all day and is recurring. This would normally be presented
after "When: xxx", e.g. "When: Tue, Mar 10, 2010 (all day, recurring)" -->
<!-- The name of this APK as shown in manage applications settings. [CHAR LIMIT=30] -->
<!-- Used as the body text of a message reporting to an attendee that a
specific instance of a recurring meeting has been canceled -->
<!-- Used as the body text of a message reporting to an attendee that a
specific instance of a recurring meeting has been changed -->
<!-- The following are a list of policies that the user's server might require, but that can't
be enforced by our device. We will list them separated by commas, as required -->
<!-- A policy in which the device may not have a storage card [CHAR LIMIT=50] -->
<!-- A policy in which the device may not have unsigned applications installed
[CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow application installation via an unsigned
installer [CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow wifi communications [CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow text messaging [CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow POP3 or IMAP email accounts [CHAR LIMIT=50] -->
<!-- A policy in which the device may allow infrared communications [CHAR LIMIT=50] -->
<!-- A policy in which the device may allow HTML email to be received [CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow the user of web browsers [CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow the receipt of consumer email
[CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow internet connection sharing
[CHAR LIMIT=50] -->
<!-- A policy in which messages must be in SMIME format [CHAR LIMIT=50] -->
<!-- A policy in which the device's bluetooth capabilities are restricted [CHAR LIMIT=50] -->
<!-- A policy in which the device blocks specified applications [CHAR LIMIT=50]-->
<!-- A policy in which the device allows only specified applications [CHAR LIMIT=50] -->
<!-- A policy in which the device limits the amount of text that can be displayed for a
given message [CHAR LIMIT=50] -->
<!-- A policy in which the device limits the amount of HTML text that can be displayed for a
given message [CHAR LIMIT=50] -->
<!-- A policy in which the device requires device or sd card encryption [CHAR LIMIT=50] -->
<!-- The following are a list of policies that the user's server requires and that are
in force. We will list them separated by commas, as required -->
<!-- A policy in which attachments aren't allowed to be downloaded [CHAR LIMIT=50] -->
<!-- A policy in which the device restricts the size of attachments that can be downloaded
[CHAR LIMIT=50] -->
<!-- A policy in which the device may only sync manually while roaming [CHAR LIMIT=50] -->
<!-- The following is a policy that may or not be supported on a particular device -->
<!-- A policy in which the device requires device or sd card encryption [CHAR LIMIT=50] -->
<!-- The window length strings below MUST remain in sync with those in com.android.email -->
<!-- In account setup options & account settings screens (exchange), sync window length; this
implies loading a 'reasonable' number of messages [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- Title for notification warning about an authentication error [CHAR LIMIT=40] -->
<!-- text for notification warning about an authentication error [CHAR LIMIT=60] -->
<!-- Message displayed when there is no application to handle the settings option. [CHAR LIMIT=NONE] -->
</resources>
100 changes: 100 additions & 0 deletions res/values-ga-rIE/strings.xml
View file
@@ -0,0 +1,100 @@
<?xml version="1.0" encoding="utf-8"?>
<!--Generated by crowdin.com-->
<!-- Copyright (C) 2008 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<!-- Deprecated strings - Move the identifiers to this section, mark as
DO NOT TRANSLATE, and remove the actual text. These will be removed in a
bulk operation. -->
<!-- Do Not Translate. Unused string. -->
<!-- Short name of Microsoft Exchange account type; used by AccountManager -->
<!-- Long name of Microsoft Exchange account type; used by AccountManager -->
<!-- Message subject for meeting accepted response. This will be followed
by a colon and the title of the meeting (i.e. the title of the meeting becomes
part of the subject of the message that's sent) -->
<!-- Message subject for meeting declined response. This is followed by
a colon and the title of the meeting (i.e. the title of the meeting becomes
part of the subject of the message that's sent) -->
<!-- Message subject for meeting tentative response. This is followed by
a colon and the title of the meeting (i.e. the title of the meeting becomes
part of the subject of the message that's sent) -->
<!-- Message subject for a canceled meeting email. This is followed by a
colon and the title of the meeting (i.e. the title of the meeting becomes
part of the subject of the message that's sent) -->
<!-- Message subject for an updated meeting email. This is followed by a
colon and the title of the meeting (i.e. the title of the meeting becomes
part of the subject of the message that's sent) -->
<!-- Indicate when a meeting takes place. This is presented in in bullet
form, as in, "When: xxx" followed by "Where: xxx" -->
<!-- Indicate where a meeting takes place. This is presented in in bullet
form, as in, "When: xxx" followed by "Where: xxx" -->
<!-- Indicate that a meeting is recurring. This would normally be presented
after "When: xxx", e.g. "When: Tue, Mar 10, 2010 at 2:30pm (recurring)" -->
<!-- Indicate that a meeting lasts all day. This would normally be presented
after "When: xxx", e.g. "When: Tue, Mar 10, 2010 (all day)" -->
<!-- Indicate that a meeting lasts all day and is recurring. This would normally be presented
after "When: xxx", e.g. "When: Tue, Mar 10, 2010 (all day, recurring)" -->
<!-- The name of this APK as shown in manage applications settings. [CHAR LIMIT=30] -->
<!-- Used as the body text of a message reporting to an attendee that a
specific instance of a recurring meeting has been canceled -->
<!-- Used as the body text of a message reporting to an attendee that a
specific instance of a recurring meeting has been changed -->
<!-- The following are a list of policies that the user's server might require, but that can't
be enforced by our device. We will list them separated by commas, as required -->
<!-- A policy in which the device may not have a storage card [CHAR LIMIT=50] -->
<!-- A policy in which the device may not have unsigned applications installed
[CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow application installation via an unsigned
installer [CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow wifi communications [CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow text messaging [CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow POP3 or IMAP email accounts [CHAR LIMIT=50] -->
<!-- A policy in which the device may allow infrared communications [CHAR LIMIT=50] -->
<!-- A policy in which the device may allow HTML email to be received [CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow the user of web browsers [CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow the receipt of consumer email
[CHAR LIMIT=50] -->
<!-- A policy in which the device may not allow internet connection sharing
[CHAR LIMIT=50] -->
<!-- A policy in which messages must be in SMIME format [CHAR LIMIT=50] -->
<!-- A policy in which the device's bluetooth capabilities are restricted [CHAR LIMIT=50] -->
<!-- A policy in which the device blocks specified applications [CHAR LIMIT=50]-->
<!-- A policy in which the device allows only specified applications [CHAR LIMIT=50] -->
<!-- A policy in which the device limits the amount of text that can be displayed for a
given message [CHAR LIMIT=50] -->
<!-- A policy in which the device limits the amount of HTML text that can be displayed for a
given message [CHAR LIMIT=50] -->
<!-- A policy in which the device requires device or sd card encryption [CHAR LIMIT=50] -->
<!-- The following are a list of policies that the user's server requires and that are
in force. We will list them separated by commas, as required -->
<!-- A policy in which attachments aren't allowed to be downloaded [CHAR LIMIT=50] -->
<!-- A policy in which the device restricts the size of attachments that can be downloaded
[CHAR LIMIT=50] -->
<!-- A policy in which the device may only sync manually while roaming [CHAR LIMIT=50] -->
<!-- The following is a policy that may or not be supported on a particular device -->
<!-- A policy in which the device requires device or sd card encryption [CHAR LIMIT=50] -->
<!-- The window length strings below MUST remain in sync with those in com.android.email -->
<!-- In account setup options & account settings screens (exchange), sync window length; this
implies loading a 'reasonable' number of messages [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- A sync window length setting (i.e. load messages this far back) [CHAR LIMIT=25] -->
<!-- Title for notification warning about an authentication error [CHAR LIMIT=40] -->
<!-- text for notification warning about an authentication error [CHAR LIMIT=60] -->
<!-- Message displayed when there is no application to handle the settings option. [CHAR LIMIT=NONE] -->
</resources>
1 change: 1 addition & 0 deletions res/values-ug/strings.xml
View file
Expand Up @@ -21,6 +21,7 @@
<!-- Do Not Translate. Unused string. -->
<!-- Short name of Microsoft Exchange account type; used by AccountManager -->
<!-- Long name of Microsoft Exchange account type; used by AccountManager -->
<string name="exchange_name_alternate">Microsoft Exchange ActiveSync</string>
<!-- Message subject for meeting accepted response. This will be followed
by a colon and the title of the meeting (i.e. the title of the meeting becomes
part of the subject of the message that's sent) -->
Expand Down

0 comments on commit 376b4b0

Please sign in to comment.