TheArchive/session-android
1
0
Fork 0
mirror of https://github.com/oxen-io/session-android.git synced 2024-11-24 02:25:19 +00:00
Code Issues Packages Projects Releases Wiki Activity
43214a854c
session-android/res/values/strings.xml

517 lines
42 KiB
XML
Raw Normal View History

Initial Project Import
2011-12-20 18:20:44 +00:00
<?xml version="1.0" encoding="utf-8"?>
<resources>
<string name="app_name">TextSecure</string>
<string name="yes">Yes</string>
<string name="no">No</string>
Localisation commit You know, it's much more fun listening to you in a lecture theatre. :-P Right; any nit picks now might have to wait 3 weeks, depending on available connectivity. Hope I did not screw this one up.
2012-09-22 19:53:56 +00:00
<string name="delete">Delete</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- ApplicationExportManager -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="ApplicationExportManager_import_database_and_settings_title">Import Database and Settings?</string>
<string name="ApplicationExportManager_import_database_and_settings_message">Import TextSecure database, keys, and settings from the SD Card?\n\nWARNING: This will clobber any existing messages, keys, and settings!</string>
<string name="ApplicationExportManager_importing_database_and_keys">Importing Database and Keys</string>
<string name="ApplicationExportManager_importing_your_sms_database_keys_and_settings">Importing your SMS database, keys, and settings...</string>
<string name="ApplicationExportManager_export_database_question">Export Database?</string>
<string name="ApplicationExportManager_export_textsecure_database_keys_and_settings_prompt">Export TextSecure database, keys, and settings to the SD Card?</string>
<string name="ApplicationExportManager_exporting_database_and_keys">Exporting Database and Keys</string>
<string name="ApplicationExportManager_exporting_your_sms_database_keys_and_settings">Exporting your SMS database, keys, and settings...</string>
<string name="ApplicationExportManager_no_sd_card_found_exclamation">No SD card found!</string>
<string name="ApplicationExportManager_error_exporting_to_sd_exclamation">Error exporting to SD!</string>
<string name="ApplicationExportManager_import_successful_exclamation">Import Successful!</string>
<string name="ApplicationExportManager_export_successful_exclamation">Export Successful!</string>
Localisation commit You know, it's much more fun listening to you in a lecture theatre. :-P Right; any nit picks now might have to wait 3 weeks, depending on available connectivity. Hope I did not screw this one up.
2012-09-22 19:53:56 +00:00
<string name="ApplicationExportManager_import">Import</string>
<string name="ApplicationExportManager_export">Export</string>
Resource cleanup
2013-02-19 18:36:48 +00:00
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- ApplicationPreferencesActivity -->
Improve support for "me" contact. 1) Add >= ICS profile support (the system-supported "me" contact). 2) Improve <= Gingerbread support for me contact by auto-detecting contacts that have the same number as the SIM card. 3) Tie in identity key import/export support to the "me" contact. 4) Don't display a "me" selection option in preference if it can be auto-detected. 5) Refactor out the ContactAccessorNewApi back into the base class.
2012-10-23 02:17:08 +00:00
<string name="ApplicationPreferencesActivity_currently_s">Currently: %s</string>
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="ApplicationPreferenceActivity_not_found_exclamation">Not found!</string>
<string name="ApplicationPreferenceActivity_no_valid_identity_key_was_found_in_the_specified_contact">No valid identity key was found in the specified contact.</string>
<string name="ApplicationPreferenceActivity_you_don_t_have_an_identity_key_exclamation">You don\'t have an identity key!</string>
<string name="ApplicationPreferenceActivity_you_have_not_yet_defined_a_contact_for_yourself">You have not yet defined a contact for yourself! Select one in the Settings menu.</string>
<string name="ApplicationPreferenceActivity_exported_to_contacts_database">Exported to contacts database!</string>
<string name="ApplicationPreferenceActivity_you_need_to_have_entered_your_passphrase_before_importing_keys">You need to have entered your passphrase before importing keys...</string>
<string name="ApplicationPreferenceActivity_you_need_to_have_entered_your_passphrase_before_managing_keys">You need to have entered your passphrase before managing keys...</string>
<string name="ApplicationPreferenceActivity_you_havent_set_a_passphrase_yet">You haven\'t set a passphrase yet!</string>
Support for auto-deleting old messages beyond a certain conversation thread length.
2013-01-10 05:06:56 +00:00
<string name="ApplicationPreferencesActivity_messages_per_conversation">messages per conversation</string>
<string name="ApplicationPreferencesActivity_delete_all_old_messages_now">Delete all old messages now?</string>
<string name="ApplicationPreferencesActivity_are_you_sure_you_would_like_to_immediately_trim_all_conversation_threads_to_the_s_most_recent_messages">Are you sure you would like to immediately trim all conversation threads to the %s most recent messages?</string>
<string name="ApplicationPreferencesActivity_delete">Delete</string>
Added Play Store description to strings file (for translation).
2012-10-16 02:58:16 +00:00
<!-- AttachmentTypeSelectorAdapter -->
<string name="AttachmentTypeSelectorAdapter_picture">Picture</string>
<string name="AttachmentTypeSelectorAdapter_video">Video</string>
<string name="AttachmentTypeSelectorAdapter_audio">Audio</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- ConversationItem -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="ConversationItem_message_size_d_kb">Message size: %d KB</string>
<string name="ConversationItem_expires_s">Expires: %s</string>
<string name="ConversationItem_error_sending_message">Error sending message</string>
<string name="ConversationItem_sending">Sending...</string>
<string name="ConversationItem_saving_attachment">Saving Attachment</string>
<string name="ConversationItem_saving_attachment_to_sd_card">Saving attachment to SD card...</string>
<string name="ConversationItem_save_to_sd_card">Save to SD Card?</string>
<string name="ConversationItem_this_media_has_been_stored_in_an_encrypted_database_warning">This media has been stored in an encrypted database. The version you save to the SD card will no longer be encrypted, would you like to continue?</string>
<string name="ConversationItem_error_while_saving_attachment_to_sd_card">Error while saving attachment to SD card!</string>
<string name="ConversationItem_success_exclamation">Success!</string>
<string name="ConversationItem_unable_to_write_to_sd_card_exclamation">Unable to write to SD Card!</string>
<string name="ConversationItem_view_secure_media_question">View secure media?</string>
<string name="ConversationItem_this_media_has_been_stored_in_an_encrypted_database_external_viewer_warning">This media has been stored in an encrypted database. Unfortunately, to view it with an external content viewer currently requires the data to be temporarily decrypted and written to disk. Are you sure that you would like to do this?</string>
<string name="ConversationItem_key_exchange_message">Key exchange message</string>
<string name="ConversationItem_received_and_processed_key_exchange_message">Received and processed key exchange message.</string>
<string name="ConversationItem_error_received_stale_key_exchange_message">Error, received stale key exchange message.</string>
<string name="ConversationItem_received_key_exchange_message_click_to_process">Received key exchange message, click to process</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- ConversationActivity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="ConversationActivity_initiate_secure_session_question">Initiate Secure Session?</string>
<string name="ConversationActivity_initiate_secure_session_with_s_question">Initiate secure session with %s?</string>
<string name="ConversationActivity_abort_secure_session_confirmation">Abort Secure Session Confirmation</string>
<string name="ConversationActivity_are_you_sure_that_you_want_to_abort_this_secure_session_question">Are you sure that you want to abort this secure session?</string>
<string name="ConversationActivity_delete_thread_confirmation">Delete Thread Confirmation</string>
<string name="ConversationActivity_are_you_sure_that_you_want_to_permanently_delete_this_conversation_question">Are you sure that you want to permanently delete this conversation?</string>
<string name="ConversationActivity_add_attachment">Add attachment</string>
<string name="ConversationActivity_compose_message">Compose Message</string>
<string name="ConversationActivity_sorry_there_was_an_error_setting_your_attachment">Sorry, there was an error setting your attachment.</string>
<string name="ConversationActivity_sorry_the_selected_video_exceeds_message_size_restrictions">Sorry, the selected video exceeds message size restrictions.</string>
<string name="ConversationActivity_sorry_the_selected_audio_exceeds_message_size_restrictions">Sorry, the selected audio exceeds message size restrictions.</string>
<string name="ConversationActivity_recipient_is_not_a_valid_sms_or_email_address_exclamation">Recipient is not a valid SMS or email address!</string>
<string name="ConversationActivity_message_is_empty_exclamation">Message is empty!</string>
Localisation change Localisation of the message prefix when forwarding a message (in Norwegian, this would be "VS:" for instance).
2012-10-12 10:00:34 +00:00
<string name="ConversationActivity_forward_message_prefix">FWD</string>
Improve UI for group SMS ConversationActivity 1) Change title to indicate it's a group message, and specify the number of recipients. 2) Add an ActionBar icon to display a list of the recipients.
2012-10-21 21:34:09 +00:00
<string name="ConversationActivity_group_conversation_recipients">Group Conversation Recipients</string>
<string name="ConversationActivity_group_conversation">Group Conversation</string>
<string name="ConversationActivity_d_recipients_in_group">%d recipients in group</string>
Export stray strings for localization.
2013-02-04 19:12:03 +00:00
<string name="ConversationActivity_saving_draft">Saving draft...</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- ConversationFragment -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="ConversationFragment_message_details">Message details</string>
<string name="ConversationFragment_sender_s_transport_s_sent_received_s">Sender: %1$s\nTransport: %2$s\nSent/Received:%3$s</string>
Display both sent and received time in message details. 1) We record time sent in SMS database (date_sent). 2) We record time received in MMS database (date_received). 3) We union this information correctly in MmsSmsDatabase.
2013-01-06 21:13:14 +00:00
<string name="ConversationFragment_sender_s_transport_s_sent_s_received_s">Sender: %1$s\nTransport: %2$s\nSent: %3$s\nReceived:%4$s</string>
Localisation commit You know, it's much more fun listening to you in a lecture theatre. :-P Right; any nit picks now might have to wait 3 weeks, depending on available connectivity. Hope I did not screw this one up.
2012-09-22 19:53:56 +00:00
<string name="ConversationFragment_confirm_message_delete">Confirm Message Delete</string>
<string name="ConversationFragment_are_you_sure_you_want_to_permanently_delete_this_message">Are you sure that you want to permanently delete this message?</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- ConversationListAdapter -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="ConversationListAdapter_encrypted_message_enter_passphrase">"Encrypted message, enter passphrase... "</string>
<string name="ConversationListAdapter_key_exchange_message">Key exchange message...</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- ConversationListFragment -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="ConversationListFragment_delete_threads_question">Delete threads?</string>
<string name="ConversationListFragment_are_you_sure_you_wish_to_delete_all_selected_conversation_threads">Are you sure you wish to delete ALL selected conversation threads?</string>
Export stray strings for localization.
2013-02-04 19:12:03 +00:00
<string name="ConversationListFragment_deleting">Deleting</string>
<string name="ConversationListFragment_deleting_selected_threads">Deleting selected threads...</string>
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<!-- ConversationListItem -->
<string name="ConversationListItem_key_exchange_message">Key exchange message...</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- KeyScanningActivity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="KeyScanningActivity_no_scanned_key_found_exclamation">No scanned key found!</string>
Change MMS network request pattern. Currently we're flipping the radio in "MMS" mode, and connecting through any proxies specified in the APN. This always work, or at least doesn't seem to work on Sprint, since the configured mms proxy rejects proxy requests. Instead we try the following in this order: 1) Connect over normal data connection directly to MMSC. 2) Connect over MMS radio connection to MMSC. 3) Connect over MMS radio connection with any configured proxy to MMSC. Hopefully this doesn't fuck up shit on other unknown networks.
2013-02-21 02:10:33 +00:00
<!-- MmsDownloader -->
<string name="MmsDownloader_no_connectivity_available_for_mms_download_try_again_later">No connectivity available for MMS download, try again later...</string>
<string name="MmsDownloader_error_storing_mms">Error storing MMS!</string>
Major storage layer refactoring to set the stage for clean GCM. 1) We now try to hand out cursors at a minimum. There has always been a fairly clean insertion layer that handles encrypting message bodies, but the process of decrypting message bodies has always been less than ideal. Here we introduce a "Reader" interface that will decrypt message bodies when appropriate and return objects that encapsulate record state. No more MessageDisplayHelper. The MmsSmsDatabase interface is also more sane. 2) We finally rid ourselves of the technical debt associated with TextSecure's initial usage of the default SMS DB. In that world, we weren't able to use anything other than the default "Inbox, Outbox, Sent" types to describe a message, and had to overload the message content itself with a set of local "prefixes" to describe what it was (encrypted, asymetric encrypted, remote encrypted, a key exchange, procssed key exchange), and so on. This includes a major schema update that transforms the "type" field into a bitmask that describes everything that used to be encoded in a prefix, and prefixes have been completely eliminated from the system. No more Prefix.java 3) Refactoring of the MultipartMessageHandler code. It's less of a mess, and hopefully more clear as to what's going on. The next step is to remove what we can from SmsTransportDetails and genericize that interface for a GCM equivalent.
2013-04-20 19:22:04 +00:00
<string name="MmsDownloader_error_connecting_to_mms_provider">Error connecting to MMS provider...</string>
<!-- NotificationMmsMessageRecord -->
<string name="NotificationMmsMessageRecord_multimedia_message">Multimedia Message</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- PassphraseChangeActivity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="PassphraseChangeActivity_passphrases_dont_match_exclamation">Passphrases Don\'t Match!</string>
<string name="PassphraseChangeActivity_incorrect_old_passphrase_exclamation">Incorrect old passphrase!</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- PassphraseCreateActivity -->
Improve passphrase and onboarding UI. Abstract out routing. 1) Update the create, prompt, and change passphrase activities. They are no longer dialog themed, and should look a little less ugly. 2) Update the import DB activity to be less ugly and more robust. 3) Abstract all of the state handling stuff out of ConversationListActivity. This is now handled by RoutingActivity, which all launch intents move through.
2013-02-17 19:42:30 +00:00
<string name="PassphraseCreateActivity_passphrases_dont_match">Passphrases don\'t match</string>
<string name="PassphraseCreateActivity_you_must_specify_a_password">You must specify a password</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- PassphrasePromptActivity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="PassphrasePromptActivity_invalid_passphrase_exclamation">Invalid Passphrase!</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
Prompt user for APN details when missing. If TextSecure is running on a device without APN details, we prompt the user to manually specify them when the user goes to send an MMS message.
2013-03-05 01:43:04 +00:00
<!-- PromptApnActivity -->
<string name="PromptApnActivity_you_must_specify_an_mmsc_url_for_your_carrier">You must specify an MMSC URL for your carrier.</string>
<string name="PromptApnActivity_mms_settings_updated">MMS Settings Updated</string>
<string name="PromptApnActivity_you_can_modify_these_values_from_the_textsecure_settings_menu_at_any_time_">You can modify these values from the TextSecure settings menu at any time.</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- ReceiveKeyActivity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="ReceiveKeyActivity_error_you_have_received_a_corrupted_public_key">ERROR:\n\nYou have received a corrupted public key. This key can not be processed, please re-initiate a secure session.</string>
<string name="ReceiveKeyActivity_error_you_have_received_a_public_key_from_an_unsupported_version_of_the_protocol">ERROR:\n\nYou have received a public key from an unsupported version of the protocol. This key can not be processed, please re-initiate a secure session.</string>
<string name="ReceiveKeyActivity_this_key_exchange_message_does_not_include_an_identity_signature">This key exchange message does not include an identity signature.</string>
<string name="ReceiveKeyActivity_this_key_exchange_message_includes_an_identity_signature_but_you_do_not_yet_trust_it">This key exchange message includes an identity signature, but you do not yet trust it.</string>
<string name="ReceiveKeyActivity_this_key_exchange_message_includes_an_identity_signature_which_you_trust_for_s">This key exchange message includes an identity signature which you trust for: %s</string>
<string name="ReceiveKeyActivity_this_is_the_key_that_you_sent_to_start_your_current_encrypted_session_with_s">This is the key that you sent to start your current encrypted session with %s</string>
<string name="ReceiveKeyActivity_this_is_the_key_that_you_received_to_start_your_current_encrypted_session_with_s">This is the key that you received to start your current encrypted session with %s</string>
<string name="ReceiveKeyActivity_you_have_received_a_key_exchange_message_from_s_warning_you_already_have_an_encrypted_session">You have received a Key Exchange message from %s.\n\nWARNING: You already have an encrypted session with this contact. If you choose to accept this key exchange message, it will destroy your existing session and you will have to re-authenticate. Would you like to complete this key exchange?</string>
<string name="ReceiveKeyActivity_you_have_received_a_key_exchange_message_from_s_you_have_previously_initiated">You have received a Key Exchange message from %s. You have previously initiated a session with this contact, and by accepting this key you will complete the key exchange. Would you like to complete this key exchange?</string>
<string name="ReceiveKeyActivity_you_have_initiated_a_key_exchange_message_with_s_but_have_not_yet_received_a_reply">You have initiated a Key Exchange message with %s but have not yet received a reply.</string>
<string name="ReceiveKeyActivity_you_have_received_a_key_exchange_message_from_s_you_have_no_existing_session">You have received a Key Exchange message from %s. You have no existing session with this contact, would you like to complete this key exchange?</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- ReviewIdentitiesActivity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="ReviewIdentitiesActivity_unable_to_view_corrupted_identity_key_exclamation">Unable to view corrupted identity key!</string>
Localisation commit You know, it's much more fun listening to you in a lecture theatre. :-P Right; any nit picks now might have to wait 3 weeks, depending on available connectivity. Hope I did not screw this one up.
2012-09-22 19:53:56 +00:00
<string name="ReviewIdentitiesActivity_delete_identity">Delete identity?</string>
<string name="ReviewIdentitiesActivity_delete_identity_are_you_sure_you_want_to_delete_this_identity_key">Are you sure that you wish to permanently delete this identity key?</string>
<string name="ReviewIdentitiesActivity_invalid_identity">Invalid Identity!</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- SaveIdentityActivity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="SaveIdentityActivity_you_must_specify_a_name_for_this_identity_exclamation">You must specify a name for this identity!</string>
<string name="SaveIdentityActivity_identity_name_exists_exclamation">Identity Name Exists!</string>
<string name="SaveIdentityActivity_an_identity_key_with_the_specified_name_already_exists">An identity key with the specified name already exists.</string>
<string name="SaveIdentityActivity_manage_identities">Manage Identities</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- VerifyIdentityActivity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="VerifyIdentityActivity_mark_identity_verified_question">Mark Identity Verified?</string>
<string name="VerifyIdentityActivity_are_you_sure_you_have_validated_the_recipients_identity_fingerprint_and_would_like_to_mark_it_as_verified">Are you sure you have validated the recipients\' identity fingerprint and would like to mark it as verified?</string>
<string name="VerifyIdentityActivity_mark_verified">Mark Verified</string>
<string name="VerifyIdentityActivity_you_do_not_have_an_identity_key">You do not have an identity key.</string>
<string name="VerifyIdentityActivity_recipient_has_no_identity_key">Recipient has no identity key.</string>
<string name="VerifyIdentityActivity_recipient_has_no_identity_key_exclamation">Recipient has no identity key!</string>
<string name="VerifyIdentityActivity_scan_their_key_to_compare">Scan their key to compare</string>
<string name="VerifyIdentityActivity_get_my_key_scanned">Get my key scanned</string>
<string name="VerifyIdentityActivity_warning_the_scanned_key_does_not_match_please_check_the_fingerprint_text_carefully">WARNING, the scanned key DOES NOT match! Please check the fingerprint text carefully.</string>
<string name="VerifyIdentityActivity_not_verified_exclamation">NOT Verified!</string>
<string name="VerifyIdentityActivity_their_key_is_correct_it_is_also_necessary_to_verify_your_key_with_them_as_well">Their key is correct. It is also necessary to verify your key with them as well.</string>
<string name="VerifyIdentityActivity_verified_exclamation">Verified!</string>
<string name="VerifyIdentityActivity_you_don_t_have_an_identity_key_exclamation">You don\'t have an identity key!</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- VerifyImportedIdentityActivity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="VerifyImportedIdentityActivity_you_must_specify_a_name_for_this_contact_exclamation">You must specify a name for this contact!</string>
<string name="VerifyImportedIdentityActivity_save_identity_key_question">Save Identity Key?</string>
<string name="VerifyImportedIdentityActivity_error_saving_identity_key_exclamation">Error saving identity key!</string>
<string name="VerifyImportedIdentityActivity_this_identity_key_or_an_identity_key_with_the_same_name_already_exists_please_edit_your_key_database">This identity key or an identity key with the same name already exists. Please edit your key database.</string>
<string name="VerifyImportedIdentityActivity_scan_to_compare">Scan to compare</string>
<string name="VerifyImportedIdentityActivity_get_scanned_to_compare">Get scanned to compare</string>
<string name="VerifyImportedIdentityActivity_not_verified_exclamation">NOT Verified!</string>
<string name="VerifyImportedIdentityActivity_warning_the_scanned_key_does_not_match_exclamation">WARNING, the scanned key DOES NOT match!</string>
<string name="VerifyImportedIdentityActivity_the_scanned_key_matches_exclamation">The scanned key matches!</string>
<string name="VerifyImportedIdentityActivity_verified_exclamation">Verified!</string>
<string name="VerifyImportedIdentityActivity_are_you_sure_that_you_would_like_to_mark_this_as_a_valid_identity_key_for_all_future_correspondence_with_s">Are you sure that you would like to mark this as a valid identity key for all future correspondence with %s? You should only do this if you have actually verified the fingerprint.</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- VerifyKeysActivity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="VerifyKeysActivity_mark_session_verified_question">Mark Session Verified?</string>
<string name="VerifyKeysActivity_are_you_sure_that_you_have_validated_these_fingerprints_and_would_like_to_mark_this_session_as_verified">Are you sure that you have validated these fingerprints and would like to mark this session as verified?</string>
<string name="VerifyKeysActivity_mark_verified">Mark Verified</string>
<string name="VerifyKeysActivity_get_my_fingerprint_scanned">Get my fingerprint scanned</string>
<string name="VerifyKeysActivity_scan_their_fingerprint">Scan their fingerprint</string>
<string name="VerifyKeysActivity_warning_the_scanned_key_does_not_match_please_check_the_fingerprint_text_carefully2">WARNING, the scanned key DOES NOT match! Please check the fingerprint text carefully.</string>
<string name="VerifyKeysActivity_not_verified_exclamation">NOT Verified!</string>
<string name="VerifyKeysActivity_their_key_is_correct_it_is_also_necessary_to_get_your_fingerprint_scanned_as_well">Their key is correct. It is also necessary to get your fingerprint scanned as well.</string>
<string name="VerifyKeysActivity_verified_exclamation">Verified!</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- ViewIdentityActivity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="ViewIdentityActivity_you_do_not_have_an_identity_key">You do not have an identity key.</string>
<string name="ViewIdentityActivity_scan_to_compare">Scan to compare</string>
<string name="ViewIdentityActivity_get_scanned_to_compare">Get scanned to compare</string>
<string name="ViewIdentityActivity_warning_the_scanned_key_does_not_match_exclamation">WARNING, the scanned key DOES NOT match!</string>
<string name="ViewIdentityActivity_not_verified_exclamation">NOT Verified!</string>
<string name="ViewIdentityActivity_the_scanned_key_matches_exclamation">The scanned key matches!</string>
<string name="ViewIdentityActivity_verified_exclamation">Verified!</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- KeyExchangeInitiator -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="KeyExchangeInitiator_initiate_despite_existing_request_question">Initiate Despite Existing Request?</string>
<string name="KeyExchangeInitiator_youve_already_sent_a_session_initiation_request_to_this_recipient_are_you_sure">You\'ve already sent a session initiation request to this recipient, are you sure you\'d like to send another? This will invalidate the first request.</string>
<string name="KeyExchangeInitiator_send">Send</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- MessageDisplayHelper -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="MessageDisplayHelper_bad_encrypted_message">Bad encrypted message...</string>
<string name="MessageDisplayHelper_decrypting_please_wait">Decrypting, please wait...</string>
<string name="MessageDisplayHelper_message_encrypted_for_non_existing_session">Message encrypted for non-existing session...</string>
<string name="MessageDisplayHelper_decryption_error_local_message_corrupted_mac_doesn_t_match_potential_tampering_question">Decryption error: local message corrupted, MAC doesn\'t match. Potential tampering?</string>
Include incoming message body in notifications. 1) Refactor the master secret reset logic to properly interact with services. 2) Add support for "BigText" and "Inbox" style notifications. 3) Decrypt message bodies when unlocked, display 'encrypted' when locked.
2013-02-08 19:57:54 +00:00
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- MmsDatabase -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="MmsDatabase_connecting_to_mms_server">Connecting to MMS server...</string>
<string name="MmsDatabase_downloading_mms">Downloading MMS...</string>
<string name="MmsDatabase_mms_download_failed">MMS Download failed!</string>
<string name="MmsDatabase_downloading">Downloading...</string>
<string name="MmsDatabase_anonymous">Anonymous</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- MmsMessageRecord -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="MmsMessageRecord_decrypting_mms_please_wait">Decrypting MMS, please wait...</string>
<string name="MmsMessageRecord_bad_encrypted_mms_message">Bad encrypted MMS message...</string>
<string name="MmsMessageRecord_mms_message_encrypted_for_non_existing_session">MMS message encrypted for non-existing session...</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
Support for robust delivery. 1) If a message fails to be delivered, post a notification in the status bar if that thread is not active and visible. 2) If a message fails to be delivered because there is no service, keep retrying every time service becomes available again.
2013-02-09 23:17:55 +00:00
<!-- MmsSender -->
<string name="MmsSender_currently_unable_to_send_your_mms_message">Currently unable to send your MMS message. It will be sent once service becomes available.</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- ApplicationMigrationService -->
Improve passphrase and onboarding UI. Abstract out routing. 1) Update the create, prompt, and change passphrase activities. They are no longer dialog themed, and should look a little less ugly. 2) Update the import DB activity to be less ugly and more robust. 3) Abstract all of the state handling stuff out of ConversationListActivity. This is now handled by RoutingActivity, which all launch intents move through.
2013-02-17 19:42:30 +00:00
<string name="ApplicationMigrationService_import_in_progress">Import in progress</string>
<string name="ApplicationMigrationService_importing_text_messages">Importing Text Messages</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- KeyCachingService -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="KeyCachingService_textsecure_passphrase_cached">TextSecure Passphrase Cached</string>
<string name="KeyCachingService_passphrase_cached">Passphrase Cached</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- MessageNotifier -->
Include incoming message body in notifications. 1) Refactor the master secret reset logic to properly interact with services. 2) Add support for "BigText" and "Inbox" style notifications. 3) Decrypt message bodies when unlocked, display 'encrypted' when locked.
2013-02-08 19:57:54 +00:00
<string name="MessageNotifier_d_new_messages">%d new messages</string>
<string name="MessageNotifier_most_recent_from_s">Most recent from: %s</string>
<string name="MessageNotifier_key_exchange">Key exchange...</string>
<string name="MessageNotifier_encrypted_message">Encrypted message...</string>
<string name="MessageNotifier_corrupted_ciphertext">Corrupted ciphertext</string>
<string name="MessageNotifier_no_subject">(No Subject)</string>
Support for robust delivery. 1) If a message fails to be delivered, post a notification in the status bar if that thread is not active and visible. 2) If a message fails to be delivered because there is no service, keep retrying every time service becomes available again.
2013-02-09 23:17:55 +00:00
<string name="MessageNotifier_message_delivery_failed">Message delivery failed.</string>
<string name="MessageNotifier_failed_to_deliver_message">Failed to deliver message.</string>
<string name="MessageNotifier_error_delivering_message">Error delivering message.</string>
Include incoming message body in notifications. 1) Refactor the master secret reset logic to properly interact with services. 2) Add support for "BigText" and "Inbox" style notifications. 3) Decrypt message bodies when unlocked, display 'encrypted' when locked.
2013-02-08 19:57:54 +00:00
Support for robust delivery. 1) If a message fails to be delivered, post a notification in the status bar if that thread is not active and visible. 2) If a message fails to be delivered because there is no service, keep retrying every time service becomes available again.
2013-02-09 23:17:55 +00:00
<!-- SmsReceiver -->
<string name="SmsReceiver_currently_unable_to_send_your_sms_message">Currently unable to send your SMS message. It will be sent once service becomes available.</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- auto_initiate_activity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="auto_initiate_activity__you_have_received_a_message_from_someone_who_supports_textsecure_encrypted_sessions_would_you_like_to_initiate_a_secure_session">You have received a message from someone who supports TextSecure encrypted sessions. Would you like to initiate a secure session?</string>
<string name="auto_initiate_activity__initiate_exchange">Initiate Exchange</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- change_passphrase_activity -->
Improve passphrase and onboarding UI. Abstract out routing. 1) Update the create, prompt, and change passphrase activities. They are no longer dialog themed, and should look a little less ugly. 2) Update the import DB activity to be less ugly and more robust. 3) Abstract all of the state handling stuff out of ConversationListActivity. This is now handled by RoutingActivity, which all launch intents move through.
2013-02-17 19:42:30 +00:00
<string name="change_passphrase_activity__old_passphrase">OLD PASSPHRASE:</string>
<string name="change_passphrase_activity__new_passphrase">NEW PASSPHRASE:</string>
<string name="change_passphrase_activity__repeat_new_passphrase">REPEAT NEW PASSPHRASE:</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- contact_selection_group_activity -->
<!-- contact_selection_list_activity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="contact_selection_group_activity__no_contacts">No contacts.</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
Localisation commit You know, it's much more fun listening to you in a lecture theatre. :-P Right; any nit picks now might have to wait 3 weeks, depending on available connectivity. Hope I did not screw this one up.
2012-09-22 19:53:56 +00:00
<!-- ContactSelectionListFragment-->
<string name="ContactSelectionlistFragment_select_for">Select for</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- contact_selection_recent_activity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="contact_selection_recent_activity__no_recent_calls">No recent calls.</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- conversation_activity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="conversation_activity__type_message">Type message</string>
<string name="conversation_activity__send">Send</string>
<string name="conversation_activity__remove">Remove</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
Add ability to specify APN information in TextSecure settings. 1) Add configuration options for APN information in TextSecure settings. 2) Fall back to TextSecure settings if system settings are unavailable while sending/receiving MMS. 3) Catch sqlite exception when devices randomly don't have the same APN db or table structure.
2012-12-09 00:46:38 +00:00
<!-- conversation_item_sent -->
<string name="conversation_item_sent__download">Download</string>
<string name="conversation_item_sent__downloading">Downloading</string>
<!-- conversation_item_received -->
<string name="conversation_item_received__download">Download</string>
<string name="conversation_item_received__downloading">Downloading</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- conversation_fragment_cab -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="conversation_fragment_cab__batch_selection_mode">Batch Selection Mode</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- create_passphrase_activity -->
Improve passphrase and onboarding UI. Abstract out routing. 1) Update the create, prompt, and change passphrase activities. They are no longer dialog themed, and should look a little less ugly. 2) Update the import DB activity to be less ugly and more robust. 3) Abstract all of the state handling stuff out of ConversationListActivity. This is now handled by RoutingActivity, which all launch intents move through.
2013-02-17 19:42:30 +00:00
<string name="create_passphrase_activity__please_choose_a_passphrase_that_will_be_used_to_locally_encrypt_your_data_this_should_be_a_strong_passphrase">Please choose a passphrase that will be used to locally encrypt your data.\n\nThis should be a strong passphrase.</string>
<string name="create_passphrase_activity__passphrase">PASSPHRASE:</string>
<string name="create_passphrase_activity__repeat">REPEAT:</string>
<string name="create_passphrase_activity__continue">Continue</string>
<string name="create_passphrase_activity__generating_secrets">GENERATING SECRETS</string>
<!-- database_migration_activity -->
Resource cleanup
2013-02-19 18:36:48 +00:00
<string name="database_migration_activity__would_you_like_to_import_your_existing_text_messages">Would you like to import your existing text messages into TextSecure\'s encrypted database?</string>
Improve passphrase and onboarding UI. Abstract out routing. 1) Update the create, prompt, and change passphrase activities. They are no longer dialog themed, and should look a little less ugly. 2) Update the import DB activity to be less ugly and more robust. 3) Abstract all of the state handling stuff out of ConversationListActivity. This is now handled by RoutingActivity, which all launch intents move through.
2013-02-17 19:42:30 +00:00
<string name="database_migration_activity__the_default_system_database_will_not_be_modified">The default system database will not be modified or altered in any way.</string>
<string name="database_migration_activity__skip">Skip</string>
<string name="database_migration_activity__import">Import</string>
<string name="database_migration_activity__this_could_take_a_moment_please_be_patient">This could take a moment. Please be patient, we\'ll notify you when the import is complete.</string>
Major storage layer refactoring to set the stage for clean GCM. 1) We now try to hand out cursors at a minimum. There has always been a fairly clean insertion layer that handles encrypting message bodies, but the process of decrypting message bodies has always been less than ideal. Here we introduce a "Reader" interface that will decrypt message bodies when appropriate and return objects that encapsulate record state. No more MessageDisplayHelper. The MmsSmsDatabase interface is also more sane. 2) We finally rid ourselves of the technical debt associated with TextSecure's initial usage of the default SMS DB. In that world, we weren't able to use anything other than the default "Inbox, Outbox, Sent" types to describe a message, and had to overload the message content itself with a set of local "prefixes" to describe what it was (encrypted, asymetric encrypted, remote encrypted, a key exchange, procssed key exchange), and so on. This includes a major schema update that transforms the "type" field into a bitmask that describes everything that used to be encoded in a prefix, and prefixes have been completely eliminated from the system. No more Prefix.java 3) Refactoring of the MultipartMessageHandler code. It's less of a mess, and hopefully more clear as to what's going on. The next step is to remove what we can from SmsTransportDetails and genericize that interface for a GCM equivalent.
2013-04-20 19:22:04 +00:00
<string name="database_migration_activity__importing">IMPORTING</string>
<!-- database_upgrade_activity -->
<string name="database_upgrade_activity__updating_database">Updating Database...</string>
Improve passphrase and onboarding UI. Abstract out routing. 1) Update the create, prompt, and change passphrase activities. They are no longer dialog themed, and should look a little less ugly. 2) Update the import DB activity to be less ugly and more robust. 3) Abstract all of the state handling stuff out of ConversationListActivity. This is now handled by RoutingActivity, which all launch intents move through.
2013-02-17 19:42:30 +00:00
<!-- prompt_passphrase_activity -->
<string name="prompt_passphrase_activity__textsecure_passphrase">TEXTSECURE PASSPHRASE</string>
<string name="prompt_passphrase_activity__unlock">Unlock</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
Prompt user for APN details when missing. If TextSecure is running on a device without APN details, we prompt the user to manually specify them when the user goes to send an MMS message.
2013-03-05 01:43:04 +00:00
<!-- prompt_apn_activity -->
<string name="prompt_apn_activity__textsecure_requires_apn_settings_to_deliver_media_messages_via_your_wireless_carrier">TextSecure requires APN settings to deliver media messages via your wireless carrier. Your device does not make this information available, which is occasionally true for locked devices and other restrictive configurations.</string>
<string name="prompt_apn_activity__to_send_media_messages_please_complete_the_necessary_apn_information_below">To send media messages, please complete the necessary APN information below. The values for your carrier can generally be located by searching for \'&amp;lt;your carrier&amp;gt; APN\'. You will only need to do this once.</string>
<string name="prompt_apn_activity__mmsc_url_required">MMSC URL (REQUIRED):</string>
<string name="prompt_apn_activity__mms_proxy_host_optional">MMS PROXY HOST (OPTIONAL):</string>
<string name="prompt_apn_activity__mms_proxy_port_optional">MMS PROXY PORT (OPTIONAL):</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- receive_key_activity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="receive_key_activity__session">Session</string>
<string name="receive_key_activity__identities">Identities</string>
<string name="receive_key_activity__complete_exchange">Complete Exchange</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- recipients_panel -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="recipients_panel__to">To</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- review_identities -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="review_identities__you_don_t_currently_have_any_identity_keys_in_your_trust_database">You don\'t currently have any identity keys in your trust database.</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- save_identity_activity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="save_identity_activity__identity_name">Identity Name:</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- verify_identity_activity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="verify_identity_activity__their_identity_they_read">Their identity (they read):</string>
<string name="verify_identity_activity__your_identity_you_read">Your identity (you read):</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- verify_import_identity_activity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="verify_import_identity_activity__identity_name_n">Identity name:\\n</string>
<string name="verify_import_identity_activity__imported_identity_n">Imported identity:\\n</string>
<string name="verify_import_identity_activity__verified">Verified!</string>
<string name="verify_import_identity_activity__compare">Compare</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- verify_keys_activity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="verify_keys_activity__they_read_this">They read this:</string>
<string name="verify_keys_activity__you_read_this">You read this:</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- view_identity_activity -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="view_identity_activity__identity">Identity:</string>
<string name="view_identity_activity__qr_code">QR Code</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- AndroidManifest.xml -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="AndroidManifest__create_passphrase">Create Passphrase</string>
<string name="AndroidManifest__enter_passphrase">Enter Passphrase</string>
<string name="AndroidManifest__select_contacts">Select Contacts</string>
<string name="AndroidManifest__textsecure_detected">TextSecure Detected</string>
<string name="AndroidManifest__public_identity_key">Public Identity Key</string>
<string name="AndroidManifest__change_passphrase">Change Passphrase</string>
<string name="AndroidManifest__verify_session">Verify Session</string>
<string name="AndroidManifest__verify_identity">Verify Identity</string>
<string name="AndroidManifest__save_identity">Save Identity</string>
<string name="AndroidManifest__manage_identity_keys">Manage Identity Keys</string>
<string name="AndroidManifest__complete_key_exchange">Complete Key Exchange</string>
<string name="AndroidManifest__verify_imported_identity">Verify Imported Identity</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- preferences.xml -->
Make a general category, move notification settings back inline.
2013-05-06 19:45:11 +00:00
<string name="preferences__general">General</string>
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="preferences__use_settings">Use Settings</string>
Localisation commit You know, it's much more fun listening to you in a lecture theatre. :-P Right; any nit picks now might have to wait 3 weeks, depending on available connectivity. Hope I did not screw this one up.
2012-09-22 19:53:56 +00:00
<string name="preferences__pref_all_sms_title">Use for all SMS</string>
<string name="preferences__pref_all_mms_title">Use for all MMS</string>
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="preferences__use_textsecure_for_viewing_and_storing_all_incoming_text_messages">Use TextSecure for viewing and storing all incoming text messages</string>
<string name="preferences__use_textsecure_for_viewing_and_storing_all_incoming_multimedia_messages">Use TextSecure for viewing and storing all incoming multimedia messages</string>
<string name="preferences__input_settings">Input Settings</string>
Localisation commit You know, it's much more fun listening to you in a lecture theatre. :-P Right; any nit picks now might have to wait 3 weeks, depending on available connectivity. Hope I did not screw this one up.
2012-09-22 19:53:56 +00:00
<string name="preferences__pref_enter_sends_title">Enter sends</string>
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="preferences__pressing_the_enter_key_will_send_text_messages">Pressing the enter key will send text messages</string>
<string name="preferences__display_settings">Display Settings</string>
<string name="preferences__choose_identity">Choose Identity</string>
<string name="preferences__choose_your_contact_entry_from_the_contacts_list">Choose your contact entry from the contacts list.</string>
<string name="preferences__encryption_settings">Encryption Settings</string>
Sentence case settings Let's be consistent and conformant with android style guide for settings labels.
2013-03-29 01:13:38 +00:00
<string name="preferences__change_passphrase">Change passphrase</string>
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="preferences__change_my_passphrase">Change my passphrase</string>
Sentence case settings Let's be consistent and conformant with android style guide for settings labels.
2013-03-29 01:13:38 +00:00
<string name="preferences__complete_key_exchanges">Complete key exchanges</string>
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="preferences__automatically_complete_key_exchanges_for_new_sessions_or_for_existing_sessions_with_the_same_identity_key">Automatically complete key exchanges for new sessions or for existing sessions with the same identity key</string>
<string name="preferences__include_a_whitespace_tag_at_the_end_of_every_non_encrypted_message">Include a whitespace tag at the end of every non-encrypted message</string>
<string name="preferences__include_whitespace_tag">Include whitespace tag</string>
<string name="preferences__sign_key_exchange_messages_with_identity_key">Sign key exchange messages with identity key</string>
<string name="preferences__sign_key_exchange">Sign Key Exchange</string>
<string name="preferences__forget_passphrase_from_memory_after_some_interval">Forget passphrase from memory after some interval</string>
<string name="preferences__timeout_passphrase">Timeout passphrase</string>
Localisation commit You know, it's much more fun listening to you in a lecture theatre. :-P Right; any nit picks now might have to wait 3 weeks, depending on available connectivity. Hope I did not screw this one up.
2012-09-22 19:53:56 +00:00
<string name="preferences__pref_timeout_interval_dialogtitle">Select Passphrase Timeout</string>
<string name="preferences__pref_timeout_interval_title">Timeout interval</string>
<string name="preferences__the_amount_of_time_to_wait_before_forgetting_passphrase">The amount of time to wait before forgetting passphrase from memory</string>
Sentence case settings Let's be consistent and conformant with android style guide for settings labels.
2013-03-29 01:13:38 +00:00
<string name="preferences__identity_key_settings">Identity keys</string>
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="preferences__view_my_identity_key">View my identity key</string>
<string name="preferences__export_my_identity_key">Export my identity key</string>
Sentence case settings Let's be consistent and conformant with android style guide for settings labels.
2013-03-29 01:13:38 +00:00
<string name="preferences__import_contacts_key">Import contact\'s key</string>
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="preferences__import_an_identity_key_from_a_contact">Import an identity key from a contact</string>
Sentence case settings Let's be consistent and conformant with android style guide for settings labels.
2013-03-29 01:13:38 +00:00
<string name="preferences__manage_identity_keys">Manage identity keys</string>
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="preferences__manage_configured_identity_keys">Manage configured identity keys</string>
<string name="preferences__notification_settings">Notification Settings</string>
<string name="preferences__notifications">Notifications</string>
<string name="preferences__display_message_notifications_in_status_bar">Display message notifications in status bar</string>
<string name="preferences__led_color">LED Color</string>
<string name="preferences__change_notification_led_color">Change notification LED color</string>
Localisation commit You know, it's much more fun listening to you in a lecture theatre. :-P Right; any nit picks now might have to wait 3 weeks, depending on available connectivity. Hope I did not screw this one up.
2012-09-22 19:53:56 +00:00
<string name="preferences__pref_led_blink_title">LED Blink Pattern</string>
<string name="preferences__change_notification_blink_pattern">Change notification LED blink pattern</string>
<string name="preferences__pref_led_blink_dialogtitle">Select LED Blink Pattern</string>
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="preferences__select_led_color">Select LED Color</string>
Localisation commit You know, it's much more fun listening to you in a lecture theatre. :-P Right; any nit picks now might have to wait 3 weeks, depending on available connectivity. Hope I did not screw this one up.
2012-09-22 19:53:56 +00:00
<string name="preferences__select_ringtone">Select Ringtone</string>
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="preferences__vibrate">Vibrate</string>
<string name="preferences__also_vibrate_when_notified">Also vibrate when notified</string>
More localisation I knew there were some I missed out.
2012-09-22 21:34:05 +00:00
<string name="preferences__minutes">minutes</string>
<string name="preferences__hours">hours</string>
<string name="preferences__green">Green</string>
Sentence case settings Let's be consistent and conformant with android style guide for settings labels.
2013-03-29 01:13:38 +00:00
<string name="preferences__red">Red</string>
More localisation I knew there were some I missed out.
2012-09-22 21:34:05 +00:00
<string name="preferences__blue">Blue</string>
<string name="preferences__orange">Orange</string>
<string name="preferences__cyan">Cyan</string>
<string name="preferences__magenta">Magenta</string>
<string name="preferences__fast">Fast</string>
<string name="preferences__normal">Normal</string>
<string name="preferences__slow">Slow</string>
<string name="preferences__custom">Custom</string>
Reorganize settings menu Mostly xml work, with one small hack to fix the sub menu themes, found here: http://code.google.com/p/android/issues/detail?id=4611#c35
2013-03-28 12:45:07 +00:00
<string name="preferences__advanced">Advanced</string>
<string name="preferences__passphrase">Passphrase</string>
<string name="preferences__advanced_mms_access_point_names">Fallback MMSC</string>
Change wording around local APN configuration preference.
2013-01-06 22:41:07 +00:00
<string name="preferences__enable_fallback_mmsc">Enable Fallback MMSC</string>
<string name="preferences__use_mmsc_information_configured_here_when_system_apn_information_is_unavailable">Use MMSC information configured here when system APN information is unavailable.</string>
Add ability to specify APN information in TextSecure settings. 1) Add configuration options for APN information in TextSecure settings. 2) Fall back to TextSecure settings if system settings are unavailable while sending/receiving MMS. 3) Catch sqlite exception when devices randomly don't have the same APN db or table structure.
2012-12-09 00:46:38 +00:00
<string name="preferences__mmsc_url_required">MMSC URL (Required)</string>
Add proxy port option to local APN settings.
2013-01-05 23:48:29 +00:00
<string name="preferences__mms_proxy_host_optional">MMS Proxy Host (Optional)</string>
<string name="preferences__mms_proxy_port_optional">MMS Proxy Port (Optional)</string>
Support for auto-deleting old messages beyond a certain conversation thread length.
2013-01-10 05:06:56 +00:00
<string name="preferences__delivery_reports">Delivery Reports</string>
<string name="preferences__request_a_delivery_report_for_each_sms_message_you_send">Request a delivery report for each SMS message you send</string>
<string name="preferences__request_a_delivery_report_for_each_mms_message_you_send">Request a delivery report for each MMS message you send</string>
<string name="preferences__mms_delivery_reports">MMS delivery reports</string>
<string name="preferences__sms_delivery_reports">SMS delivery reports</string>
<string name="preferences__automatically_delete_older_messages_once_a_conversation_thread_exceeds_a_specified_length">Automatically delete older messages once a conversation thread exceeds a specified length</string>
<string name="preferences__delete_old_messages">Delete old messages</string>
<string name="preferences__storage">Storage</string>
<string name="preferences__conversation_length_limit">Conversation length limit</string>
<string name="preferences__trim_all_threads_now">Trim all threads now</string>
<string name="preferences__scan_through_all_conversation_threads_and_enforce_conversation_length_limits">Scan through all conversation threads and enforce conversation length limits</string>
Add ability to specify APN information in TextSecure settings. 1) Add configuration options for APN information in TextSecure settings. 2) Fall back to TextSecure settings if system settings are unavailable while sending/receiving MMS. 3) Catch sqlite exception when devices randomly don't have the same APN db or table structure.
2012-12-09 00:46:38 +00:00
More localisation I knew there were some I missed out.
2012-09-22 21:34:05 +00:00
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- **************************************** -->
<!-- menus -->
<!-- **************************************** -->
<!-- contact_selection_list -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="contact_selection_list__menu_select_all">Select All</string>
<string name="contact_selection_list__menu_unselect_all">Unselect All</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- contact_selection -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="contact_selection__menu_finished">Finished</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- conversation_button_context -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="conversation_button_context__menu_send_unencrypted">Send unencrypted</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- conversation_callable -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="conversation_callable__menu_call">Call</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- conversation_context -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="conversation_context__menu_message_details">Message details</string>
<string name="conversation_context__menu_copy_text">Copy text</string>
<string name="conversation_context__menu_delete_message">Delete message</string>
<string name="conversation_context__menu_forward_message">Forward message</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- conversation_insecure -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="conversation_insecure__menu_start_secure_session">Start Secure Session</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- conversation_list_batch -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="conversation_list_batch__menu_delete_selected">Delete Selected</string>
<string name="conversation_list_batch__menu_select_all">Select All</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- conversation_list -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="conversation_list__menu_search">Search</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- conversation_secure_verified -->
<!-- conversation_secure_unverified -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="conversation_secure_verified__menu_security">Security</string>
<string name="conversation_secure_verified__menu_verify_session">Verify Session</string>
<string name="conversation_secure_verified__menu_verify_recipient">Verify Recipient</string>
<string name="conversation_secure_verified__menu_abort_secure_session">Abort Secure Session</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- conversation -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="conversation__menu_add_attachment">Add attachment</string>
<string name="conversation__menu_delete_thread">Delete thread</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
Improve UI for group SMS ConversationActivity 1) Change title to indicate it's a group message, and specify the number of recipients. 2) Add an ActionBar icon to display a list of the recipients.
2012-10-21 21:34:09 +00:00
<!-- conversation_group_options -->
<string name="convesation_group_options__recipients_list">Recipients list</string>
String resources reorganization
2013-05-06 19:49:19 +00:00
<string name="conversation_group_options__delivery">Delivery</string>
<string name="conversation_group_options__conversation">Conversation</string>
<string name="conversation_group_options__broadcast">Broadcast</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- key_scanning -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="key_scanning__menu_compare">Compare</string>
<string name="key_scanning__menu_get_scanned_to_compare">Get scanned to compare</string>
<string name="key_scanning__menu_scan_to_compare">Scan to compare</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- text_secure_locked -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="text_secure_locked__menu_unlock">Unlock</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- text_secure_normal -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="text_secure_normal__menu_new_message">New Message</string>
<string name="text_secure_normal__menu_settings">Settings</string>
<string name="text_secure_normal__menu_import_export">Import/Export</string>
<string name="text_secure_normal__menu_import">Import</string>
<string name="text_secure_normal__menu_export">Export</string>
<string name="text_secure_normal__menu_clear_passphrase">Clear Passphrase</string>
Add 'mark all as read' option
2013-05-06 20:59:40 +00:00
<string name="text_secure_normal__mark_all_as_read">Mark All Read</string>
Extract TextSecure strings for i18n. 1) Change all instances which use concatenation to build strings with variables in them to use string formatting instead. 2) Extract all string literals from layouts and menus into strings.xml 3) Extract all string literals from code into strings.xml
2012-09-08 03:03:23 +00:00
<!-- verify_keys -->
Include source origin in string key name. This should help eliminate string duplicates, as well as provide visibility into where strings in a resource file are being used.
2012-09-20 02:56:04 +00:00
<string name="verify_keys__menu_verified">Verified</string>
Added Play Store description to strings file (for translation).
2012-10-16 02:58:16 +00:00
Improve UI for group SMS ConversationActivity 1) Change title to indicate it's a group message, and specify the number of recipients. 2) Add an ActionBar icon to display a list of the recipients.
2012-10-21 21:34:09 +00:00
<!-- Misc. piggybacking -->
merge liliakai-settings
2013-05-06 19:48:16 +00:00
Improve UI for group SMS ConversationActivity 1) Change title to indicate it's a group message, and specify the number of recipients. 2) Add an ActionBar icon to display a list of the recipients.
2012-10-21 21:34:09 +00:00
<!-- EOF -->
Major storage layer refactoring to set the stage for clean GCM. 1) We now try to hand out cursors at a minimum. There has always been a fairly clean insertion layer that handles encrypting message bodies, but the process of decrypting message bodies has always been less than ideal. Here we introduce a "Reader" interface that will decrypt message bodies when appropriate and return objects that encapsulate record state. No more MessageDisplayHelper. The MmsSmsDatabase interface is also more sane. 2) We finally rid ourselves of the technical debt associated with TextSecure's initial usage of the default SMS DB. In that world, we weren't able to use anything other than the default "Inbox, Outbox, Sent" types to describe a message, and had to overload the message content itself with a set of local "prefixes" to describe what it was (encrypted, asymetric encrypted, remote encrypted, a key exchange, procssed key exchange), and so on. This includes a major schema update that transforms the "type" field into a bitmask that describes everything that used to be encoded in a prefix, and prefixes have been completely eliminated from the system. No more Prefix.java 3) Refactoring of the MultipartMessageHandler code. It's less of a mess, and hopefully more clear as to what's going on. The next step is to remove what we can from SmsTransportDetails and genericize that interface for a GCM equivalent.
2013-04-20 19:22:04 +00:00
Initial Project Import
2011-12-20 18:20:44 +00:00
</resources>
Reference in New Issue Copy Permalink