signal-desktop/_locales/en/messages.json

852 lines
33 KiB
JSON
Raw Normal View History

2015-12-14 23:10:49 +00:00
{
"loading": {
"message": "Loading...",
"description": "Message shown on the loading screen before we've loaded any messages"
},
Full export, migration banner, and full migration workflow - behind flag (#1342) * Add support for backup and restore This first pass works for all stores except messages, pending some scaling improvements. // FREEBIE * Import of messages and attachments Properly sanitize filenames. Logging information that will help with debugging but won't threaten privacy (no contact or group names), where the on-disk directories have this information to make things human-readable FREEBIE * First fully operational single-action export and import! FREEBIE * Add migration export flow A banner alert leads to a blocking ui for the migration. We close the socket and wait for incoming messages to drain before starting the export. FREEBIE * A number of updates for the export flow 1. We don't immediately pop the directory selection dialog box, instead showing an explicit 'choose directory' button after explaining what is about to happen 2. We show a 'submit debug log' button on most steps of the process 3. We handle export errors and encourage the user to double-check their filesystem then submit their log 4. We are resilient to restarts during the process 5. We handle the user cancelling out of the directory selection dialog differently from other errors. 6. The export process is now serialized: non-messages, then messages. 7. After successful export, show where the data is on disk FREEBUE * Put migration behind a flag FREEBIE * Shut down websocket before proceeding with export FREEBIE * Add MigrationView to test/index.html to fix test FREEBIE * Remove 'Submit Debug Log' button when the export process is complete FREEBIE * Create a 'Signal Export' directory below user-chosen dir This cleans things up a bit so we don't litter the user's target directory with lots of stuff. FREEBIE * Clarify MessageReceiver.drain() method comments FREEBIE * A couple updates for clarity - event names, else handling Also the removal of wait(), which wasn't used anywhere. FREEBIE * A number of wording updates for the export flow FREEBIE * Export complete: put dir on its own line, make text selectable FREEBIE
2017-08-28 20:06:10 +00:00
"exportInstructions": {
"message": "The first step is to choose a directory to store this application's exported data. It will contain your message history and sensitive cryptographic data, so be sure to save it somewhere private.",
"description": "Description of the export process"
},
"chooseDirectory": {
Full export, migration banner, and full migration workflow - behind flag (#1342) * Add support for backup and restore This first pass works for all stores except messages, pending some scaling improvements. // FREEBIE * Import of messages and attachments Properly sanitize filenames. Logging information that will help with debugging but won't threaten privacy (no contact or group names), where the on-disk directories have this information to make things human-readable FREEBIE * First fully operational single-action export and import! FREEBIE * Add migration export flow A banner alert leads to a blocking ui for the migration. We close the socket and wait for incoming messages to drain before starting the export. FREEBIE * A number of updates for the export flow 1. We don't immediately pop the directory selection dialog box, instead showing an explicit 'choose directory' button after explaining what is about to happen 2. We show a 'submit debug log' button on most steps of the process 3. We handle export errors and encourage the user to double-check their filesystem then submit their log 4. We are resilient to restarts during the process 5. We handle the user cancelling out of the directory selection dialog differently from other errors. 6. The export process is now serialized: non-messages, then messages. 7. After successful export, show where the data is on disk FREEBUE * Put migration behind a flag FREEBIE * Shut down websocket before proceeding with export FREEBIE * Add MigrationView to test/index.html to fix test FREEBIE * Remove 'Submit Debug Log' button when the export process is complete FREEBIE * Create a 'Signal Export' directory below user-chosen dir This cleans things up a bit so we don't litter the user's target directory with lots of stuff. FREEBIE * Clarify MessageReceiver.drain() method comments FREEBIE * A couple updates for clarity - event names, else handling Also the removal of wait(), which wasn't used anywhere. FREEBIE * A number of wording updates for the export flow FREEBIE * Export complete: put dir on its own line, make text selectable FREEBIE
2017-08-28 20:06:10 +00:00
"message": "Choose directory",
"description": "Button to allow the user to export all data from app as part of migration process"
},
"exportButton": {
"message": "Export",
"desription": "Button shown on the choose directory dialog which starts the export process"
},
"exportChooserTitle": {
"message": "Choose target directory for data",
"description": "Title of the popup window used to select data storage location"
},
Full export, migration banner, and full migration workflow - behind flag (#1342) * Add support for backup and restore This first pass works for all stores except messages, pending some scaling improvements. // FREEBIE * Import of messages and attachments Properly sanitize filenames. Logging information that will help with debugging but won't threaten privacy (no contact or group names), where the on-disk directories have this information to make things human-readable FREEBIE * First fully operational single-action export and import! FREEBIE * Add migration export flow A banner alert leads to a blocking ui for the migration. We close the socket and wait for incoming messages to drain before starting the export. FREEBIE * A number of updates for the export flow 1. We don't immediately pop the directory selection dialog box, instead showing an explicit 'choose directory' button after explaining what is about to happen 2. We show a 'submit debug log' button on most steps of the process 3. We handle export errors and encourage the user to double-check their filesystem then submit their log 4. We are resilient to restarts during the process 5. We handle the user cancelling out of the directory selection dialog differently from other errors. 6. The export process is now serialized: non-messages, then messages. 7. After successful export, show where the data is on disk FREEBUE * Put migration behind a flag FREEBIE * Shut down websocket before proceeding with export FREEBIE * Add MigrationView to test/index.html to fix test FREEBIE * Remove 'Submit Debug Log' button when the export process is complete FREEBIE * Create a 'Signal Export' directory below user-chosen dir This cleans things up a bit so we don't litter the user's target directory with lots of stuff. FREEBIE * Clarify MessageReceiver.drain() method comments FREEBIE * A couple updates for clarity - event names, else handling Also the removal of wait(), which wasn't used anywhere. FREEBIE * A number of wording updates for the export flow FREEBIE * Export complete: put dir on its own line, make text selectable FREEBIE
2017-08-28 20:06:10 +00:00
"exportAgain": {
"message": "Export again",
"description": "If user has already exported once, this button allows user to do it again if needed"
},
"exportError": {
"message": "Unfortunately, something went wrong during the export. First, double-check your target empty directory for write access and enough space. Then, please submit a debug log so we can help you get migrated!",
"description": "Helper text if the user went forward on migrating the app, but ran into an error"
},
"exporting": {
"message": "Please wait while we export your data. It may take several minutes. You can still use Signal on your phone and other devices during this time.",
Full export, migration banner, and full migration workflow - behind flag (#1342) * Add support for backup and restore This first pass works for all stores except messages, pending some scaling improvements. // FREEBIE * Import of messages and attachments Properly sanitize filenames. Logging information that will help with debugging but won't threaten privacy (no contact or group names), where the on-disk directories have this information to make things human-readable FREEBIE * First fully operational single-action export and import! FREEBIE * Add migration export flow A banner alert leads to a blocking ui for the migration. We close the socket and wait for incoming messages to drain before starting the export. FREEBIE * A number of updates for the export flow 1. We don't immediately pop the directory selection dialog box, instead showing an explicit 'choose directory' button after explaining what is about to happen 2. We show a 'submit debug log' button on most steps of the process 3. We handle export errors and encourage the user to double-check their filesystem then submit their log 4. We are resilient to restarts during the process 5. We handle the user cancelling out of the directory selection dialog differently from other errors. 6. The export process is now serialized: non-messages, then messages. 7. After successful export, show where the data is on disk FREEBUE * Put migration behind a flag FREEBIE * Shut down websocket before proceeding with export FREEBIE * Add MigrationView to test/index.html to fix test FREEBIE * Remove 'Submit Debug Log' button when the export process is complete FREEBIE * Create a 'Signal Export' directory below user-chosen dir This cleans things up a bit so we don't litter the user's target directory with lots of stuff. FREEBIE * Clarify MessageReceiver.drain() method comments FREEBIE * A couple updates for clarity - event names, else handling Also the removal of wait(), which wasn't used anywhere. FREEBIE * A number of wording updates for the export flow FREEBIE * Export complete: put dir on its own line, make text selectable FREEBIE
2017-08-28 20:06:10 +00:00
"description": "Message shown on the migration screen while we export data"
},
"exportComplete": {
"message": "Your data has been exported to: <p><b>$location$</b></p> You'll be able to import this data as you set up <a target='_blank' href='https://support.whispersystems.org/hc/en-us/articles/214507138'>the new Signal Desktop</a>.",
Full export, migration banner, and full migration workflow - behind flag (#1342) * Add support for backup and restore This first pass works for all stores except messages, pending some scaling improvements. // FREEBIE * Import of messages and attachments Properly sanitize filenames. Logging information that will help with debugging but won't threaten privacy (no contact or group names), where the on-disk directories have this information to make things human-readable FREEBIE * First fully operational single-action export and import! FREEBIE * Add migration export flow A banner alert leads to a blocking ui for the migration. We close the socket and wait for incoming messages to drain before starting the export. FREEBIE * A number of updates for the export flow 1. We don't immediately pop the directory selection dialog box, instead showing an explicit 'choose directory' button after explaining what is about to happen 2. We show a 'submit debug log' button on most steps of the process 3. We handle export errors and encourage the user to double-check their filesystem then submit their log 4. We are resilient to restarts during the process 5. We handle the user cancelling out of the directory selection dialog differently from other errors. 6. The export process is now serialized: non-messages, then messages. 7. After successful export, show where the data is on disk FREEBUE * Put migration behind a flag FREEBIE * Shut down websocket before proceeding with export FREEBIE * Add MigrationView to test/index.html to fix test FREEBIE * Remove 'Submit Debug Log' button when the export process is complete FREEBIE * Create a 'Signal Export' directory below user-chosen dir This cleans things up a bit so we don't litter the user's target directory with lots of stuff. FREEBIE * Clarify MessageReceiver.drain() method comments FREEBIE * A couple updates for clarity - event names, else handling Also the removal of wait(), which wasn't used anywhere. FREEBIE * A number of wording updates for the export flow FREEBIE * Export complete: put dir on its own line, make text selectable FREEBIE
2017-08-28 20:06:10 +00:00
"description": "Message shown on the migration screen when we are done exporting data",
"placeholders": {
"location": {
"content": "$1",
"example": "/Users/someone/somewhere"
}
}
},
"installNewSignal": {
"message": "Install new Signal Desktop",
"description": "When export is complete, a button shows which sends user to Signal Desktop install instructions"
},
"importButton": {
"message": "Import",
"desription": "Button shown on the choose directory dialog which starts the import process"
},
"importChooserTitle": {
"message": "Choose directory with exported data",
"description": "Title of the popup window used to select data previously exported"
},
"importError": {
"message": "Unfortunately, something went wrong during the import. <p>First, double-check your target directory. It should start with 'Signal Export.'</p><p>Next, try with a new export of your data from the Chrome App.</p>If that still fails, please <a target='_blank' href='https://support.whispersystems.org/hc/en-us/articles/215188737-How-do-I-submit-a-debug-log-from-the-Desktop-'>submit a debug log</a> so we can help you get migrated!",
"description": "Message shown if the import went wrong."
},
"tryAgain": {
"message": "Try again",
"description": "Button shown if the user runs into an error during import, allowing them to start over"
},
"importInstructions": {
"message": "The first step is to tell us where you previously exported your Signal data. It will be a directory whose name starts with 'Signal Export.'",
"description": "Description of the export process"
},
"importing": {
"message": "Please wait while we import your data...",
"description": "Shown as we are loading the user's data from disk"
},
"importComplete": {
"message": "We've successfully loaded your data. The next step is to restart the application!",
"description": "Shown when the import is complete."
},
Full export, migration banner, and full migration workflow - behind flag (#1342) * Add support for backup and restore This first pass works for all stores except messages, pending some scaling improvements. // FREEBIE * Import of messages and attachments Properly sanitize filenames. Logging information that will help with debugging but won't threaten privacy (no contact or group names), where the on-disk directories have this information to make things human-readable FREEBIE * First fully operational single-action export and import! FREEBIE * Add migration export flow A banner alert leads to a blocking ui for the migration. We close the socket and wait for incoming messages to drain before starting the export. FREEBIE * A number of updates for the export flow 1. We don't immediately pop the directory selection dialog box, instead showing an explicit 'choose directory' button after explaining what is about to happen 2. We show a 'submit debug log' button on most steps of the process 3. We handle export errors and encourage the user to double-check their filesystem then submit their log 4. We are resilient to restarts during the process 5. We handle the user cancelling out of the directory selection dialog differently from other errors. 6. The export process is now serialized: non-messages, then messages. 7. After successful export, show where the data is on disk FREEBUE * Put migration behind a flag FREEBIE * Shut down websocket before proceeding with export FREEBIE * Add MigrationView to test/index.html to fix test FREEBIE * Remove 'Submit Debug Log' button when the export process is complete FREEBIE * Create a 'Signal Export' directory below user-chosen dir This cleans things up a bit so we don't litter the user's target directory with lots of stuff. FREEBIE * Clarify MessageReceiver.drain() method comments FREEBIE * A couple updates for clarity - event names, else handling Also the removal of wait(), which wasn't used anywhere. FREEBIE * A number of wording updates for the export flow FREEBIE * Export complete: put dir on its own line, make text selectable FREEBIE
2017-08-28 20:06:10 +00:00
"selectedLocation": {
"message": "your selected location",
"description": "Message shown as the export location if we didn't capture the target directory"
},
"upgradingDatabase": {
"message": "Upgrading database. This may take some time...",
"description": "Message shown on the loading screen when we're changing database structure on first run of a new version"
},
"loadingMessages": {
"message": "Loading messages. $count$ so far...",
"description": "Message shown on the loading screen when we're catching up on the backlog of messages",
"placeholders": {
"count": {
"content": "$1",
"example": "5"
}
}
},
"me": {
"message": "Me",
"description": "The label for yourself when shown in a group member list"
},
"view": {
"message": "View",
"description": "Used as a label on a button allowing user to see more information"
},
"youLeftTheGroup": {
"message": "You left the group",
"description": "Displayed when a user can't send a message because they have left the group"
},
"scrollDown": {
"message": "Scroll to bottom of conversation",
"description": "Alt text for button to take user down to bottom of conversation, shown when user scrolls up"
},
"messageBelow": {
"message": "New message below",
"description": "Alt text for button to take user down to bottom of conversation with a new message out of screen"
},
"messagesBelow": {
"message": "New messages below",
"description": "Alt text for button to take user down to bottom of conversation with more than one message out of screen"
},
"unreadMessage": {
"message": "1 Unread Message",
"description": "Text for unread message separator, just one message"
},
"unreadMessages": {
"message": "$count$ Unread Messages",
"description": "Text for unread message separator, with count",
"placeholders": {
"count": {
"content": "$1",
"example": "5"
}
}
},
"youMarkedAsVerified": {
"message": "You marked your safety number with $name$ as verified.",
"description": "Shown in the conversation history when the user marks a contact as verified.",
"placeholders": {
"name": {
"content": "$1",
"example": "Bob"
}
}
},
"youMarkedAsNotVerified": {
"message": "You marked your safety number with $name$ as unverified.",
"description": "Shown in the conversation history when the user marks a contact as not verified, whether on the safety number screen or by dismissing a banner or dialog.",
"placeholders": {
"name": {
"content": "$1",
"example": "Bob"
}
}
},
"youMarkedAsVerifiedOtherDevice": {
"message": "You marked your safety number with $name$ as verified from another device.",
"description": "Shown in the conversation history when we discover that the user marked a contact as verified on another device.",
"placeholders": {
"name": {
"content": "$1",
"example": "Bob"
}
}
},
"youMarkedAsNotVerifiedOtherDevice": {
"message": "You marked your safety number with $name$ as not verified from another device.",
"description": "Shown in the conversation history when we discover that the user marked a contact as not verified on another device.",
"placeholders": {
"name": {
"content": "$1",
"example": "Bob"
}
}
},
"membersNeedingVerification": {
"message": "Your safety numbers with these group members have changed since you last verified. Click a group member to see your new safety number with them.",
"description": "When there are multiple previously-verified group members with safety number changes, a banner will be shown. The list of contacts with safety number changes is shown, and this text introduces that list."
},
"changedSinceVerifiedMultiple": {
"message": "Your safety numbers with multiple group members have changed since you last verified. This could mean that someone is trying to intercept your communication or that they have simply reinstalled Signal.",
"description": "Shown on confirmation dialog when user attempts to send a message"
},
"changedSinceVerified": {
"message": "Your safety number with $name$ has changed since you last verified. This could mean that someone is trying to intercept your communication or that $name$ has simply reinstalled Signal.",
"description": "Shown on confirmation dialog when user attempts to send a message",
"placeholders": {
"name": {
"content": "$1",
"example": "Bob"
}
}
},
"changedRightAfterVerify": {
"message": "The safety number you are trying to verify has changed. Please review your new safety number with $name$. Remember, this change could mean that someone is trying to intercept your communication or that $name$ has simply reinstalled Signal.",
"description": "Shown on the safety number screen when the user has selected to verify/unverify a contact's safety number, and we immediately discover a safety number change",
"placeholders": {
"name": {
"content": "$1",
"example": "Bob"
}
}
},
"changedRecentlyMultiple": {
"message": "Your safety numbers with multiple group members have changed recently. This could mean that someone is trying to intercept your communication or that they have simply reinstalled Signal.",
"description": "Shown on confirmation dialog when user attempts to send a message"
},
"changedRecently": {
"message": "Your safety number with $name$ has changed recently. This could mean that someone is trying to intercept your communication or that $name$ has simply reinstalled Signal.",
"description": "Shown on confirmation dialog when user attempts to send a message",
"placeholders": {
"name": {
"content": "$1",
"example": "Bob"
}
}
},
"identityKeyErrorOnSend": {
"message": "Your safety number with $name$ has changed. This could either mean that someone is trying to intercept your communication or that $name$ has simply reinstalled Signal. You may wish to verify your saftey number with this contact.",
"description": "Shown when user clicks on a failed recipient in the message detail view after an identity key change",
"placeholders": {
"name": {
"content": "$1",
"example": "Bob"
}
}
},
"sendAnyway": {
"message": "Send Anyway",
"description": "Used on a warning dialog to make it clear that it might be risky to send the message."
},
"noLongerVerified": {
"message": "Your safety number with $name$ has changed and is no longer verified. Click to show.",
"description": "Shown in converation banner when user's safety number has changed, but they were previously verified.",
"placeholders": {
"name": {
"content": "$1",
"example": "Bob"
}
}
},
"multipleNoLongerVerified": {
"message": "Your safety numbers with multiple members of this group have changed and are no longer verified. Click to show.",
"description": "Shown in conversation banner when more than one group member's safety number has changed, but they were previously verified."
},
2015-12-26 07:01:22 +00:00
"debugLogExplanation": {
"message": "This log will be posted publicly online for contributors to view. You may examine and edit it before submitting."
},
"reportIssue": {
"message": "Report an issue",
"description": "Link to open the issue tracker"
},
2015-12-26 07:01:22 +00:00
"gotIt": {
2016-03-03 12:08:01 +00:00
"message": "Got it!",
"description": "Label for a button that dismisses a dialog. The user clicks it to confirm that they understand the message in the dialog."
2015-12-26 07:01:22 +00:00
},
"submit": {
"message": "Submit"
},
2015-12-26 06:47:09 +00:00
"verifyContact": {
"message": "You may wish to $tag_start$ verify $tag_end$ your safety number with this contact.",
"description": "Use $tag_start$ and $tag_end$ to wrap the word or phrase in this sentence that the user should click on in order to navigate to the verification screen. These placeholders will be replaced with appropriate HTML code.",
"placeholders": {
"tag_start": {
"content": "<a class='verify' href='#'>"
},
"tag_end": {
"content": "</a>"
}
}
2015-12-26 06:47:09 +00:00
},
"acceptNewKey": {
"message": "Accept",
"description": "Label for a button to accept a new safety number"
2015-12-26 06:47:09 +00:00
},
"verify": {
"message": "Mark as verified"
},
"unverify": {
"message": "Mark as not verified"
},
"isVerified": {
"message": "You have verified your safety number with $name$.",
"description": "Summary state shown at top of the safety number screen if user has verified contact.",
"placeholders": {
"name": {
"content": "$1",
"example": "Bob"
}
}
},
"isNotVerified": {
"message": "You have not verified your safety number with $name$.",
"description": "Summary state shown at top of the safety number screen if user has not verified contact.",
"placeholders": {
"name": {
"content": "$1",
"example": "Bob"
}
}
},
"verified": {
"message": "Verified"
},
"newIdentity": {
"message": "New safety number",
"description": "Header for a key change dialog"
},
"identityChanged": {
"message": "Your safety number with this contact has changed. This could either mean that someone is trying to intercept your communication, or this contact simply reinstalled Signal. You may wish to verify the new safety number below."
},
"incomingError": {
"message": "Error handling incoming message."
},
2015-12-26 05:12:17 +00:00
"unsupportedAttachment": {
"message": "Unsupported attachment type. Click to save.",
"description": "Displayed for incoming unsupported attachment"
},
"clickToSave": {
"message": "Click to save",
"description": "Hover text for attachment filenames"
},
"unnamedFile": {
"message": "Unnamed File",
"description": "Hover text for attachment filenames"
},
"voiceMessage": {
"message": "Voice Message",
"description": "Name for a voice message attachment"
},
"unsupportedFileType": {
2015-12-26 05:12:17 +00:00
"message": "Unsupported file type",
"description": "Displayed for outgoing unsupported attachment"
},
2015-12-26 04:38:16 +00:00
"fileSizeWarning": {
"message": "Sorry, the selected file exceeds message size restrictions."
},
2015-12-26 02:16:38 +00:00
"disconnected": {
"message": "Disconnected",
"description": "Displayed when the desktop client cannot connect to the server."
2015-12-26 02:16:38 +00:00
},
"connecting": {
"message": "Connecting",
"description": "Displayed when the desktop client is currently connecting to the server."
},
"offline": {
"message": "Offline",
"description": "Displayed when the desktop client has no network connection."
},
"checkNetworkConnection": {
"message": "Check your network connection.",
"description": "Obvious instructions for when a user's computer loses its network connection"
},
"attemptingReconnection": {
"message": "Attempting reconnect in $reconnect_duration_in_seconds$ seconds",
"placeholders": {
"reconnect_duration_in_seconds": {
"content": "$1",
"example": "10"
}
}
},
2015-12-26 02:15:04 +00:00
"submitDebugLog": {
"message": "Submit debug log",
"description": "Menu item and header text for debug log modal, title case."
2015-12-26 02:15:04 +00:00
},
"searchForPeopleOrGroups": {
"message": "Search...",
2015-12-26 02:15:04 +00:00
"description": "Placeholder text in the search input"
},
"welcomeToSignal": {
"message": "Welcome to Signal"
},
"selectAContact": {
"message": "Select a contact or group to start chatting."
},
2015-12-26 00:52:04 +00:00
"ok": {
"message": "OK"
},
"cancel": {
"message": "Cancel"
},
2015-12-25 06:55:53 +00:00
"failedToSend": {
"message": "Failed to send to some recipients. Check your network connection."
2015-12-25 06:55:53 +00:00
},
"error": {
"message": "Error"
},
"resend": {
"message": "Resend"
},
"messageDetail": {
"message": "Message Detail"
},
2017-07-12 22:19:07 +00:00
"delete": {
"message": "Delete"
},
"deleteWarning": {
"message": "Are you sure? Clicking 'delete' will permanently remove this message from this device."
},
"deleteMessage": {
"message": "Delete this message"
},
"from": {
"message": "From",
"description": "Label for the sender of a message"
},
"to": {
"message": "To",
"description": "Label for the receiver of a message"
},
2015-12-25 06:55:53 +00:00
"sent": {
"message": "Sent",
"description": "Label for the time a message was sent"
},
"received": {
"message": "Received",
"description": "Label for the time a message was received"
},
2015-12-25 06:50:27 +00:00
"sendMessage": {
"message": "Send a message",
"description": "Placeholder text in the message entry field"
},
"groupMembers": {
"message": "Group members"
},
"showMembers": {
"message": "Show members"
2015-12-25 06:50:27 +00:00
},
"resetSession": {
"message": "Reset session",
"description": "This is a menu item for resetting the session, using the imperative case, as in a command."
2015-12-25 06:50:27 +00:00
},
"showSafetyNumber": {
"message": "Show safety number"
},
"verifyHelp": {
"message": "If you wish to verify the security of your end-to-end encryption with $name$, compare the numbers above with the numbers on their device.",
"placeholders": {
"name": {
"content": "$1",
"example": "John"
}
}
},
"theirIdentityUnknown": {
"message": "You haven't exchanged any messages with this contact yet. Your safety number with them will be available after the first message."
},
2015-12-25 06:50:27 +00:00
"deleteMessages": {
"message": "Delete messages",
"description": "Menu item for deleting messages, title case."
2015-12-25 06:52:50 +00:00
},
"deleteConversationConfirmation": {
"message": "Permanently delete this conversation?",
"description": "Confirmation dialog text that asks the user if they really wish to delete the conversation. Answer buttons use the strings 'ok' and 'cancel'. The deletion is permanent, i.e. it cannot be undone."
},
2015-12-25 06:52:50 +00:00
"sessionEnded": {
"message": "Secure session reset",
"description": "This is a past tense, informational message. In other words, your secure session has been reset."
},
"installWelcome": {
"message": "Welcome to Signal Desktop",
"description": "Welcome title on the install page"
},
"installTagline": {
"message": "Privacy is possible. Signal makes it easy.",
"description": "Tagline displayed under 'installWelcome' string on the install page"
},
"installNew": {
"message": "Set up as new install",
"description": "One of two choices presented on the screen shown on first launch"
},
"installImport": {
"message": "Set up with Chrome App export",
"description": "One of two choices presented on the screen shown on first launch"
},
"installGetStartedButton": {
"message": "Get started"
},
"installSignalLink": {
"message": "First, install <a $a_params$>Signal</a> on your mobile phone. We'll link your devices and keep your messages in sync.",
"description": "Prompt the user to install Signal on their phone before linking",
"placeholders": {
"a_params": {
"content": "$1",
"example": "href='http://example.com'"
}
}
},
"installSignalLinks": {
"message": "First, install Signal on your <a $play_store$>Android</a> or <a $app_store$>iPhone</a>.<br /> We'll link your devices and keep your messages in sync.",
"description": "Prompt the user to install Signal on their phone before linking",
"placeholders": {
"play_store": {
"content": "$1",
"example": "href='http://example.com'"
},
"app_store": {
"content": "$2",
"example": "href='http://example.com'"
}
}
},
"installGotIt": {
"message": "Got it",
"description": "Button for the user to confirm that they have Signal installed."
},
"installIHaveSignalButton": {
"message": "I have Signal for Android",
"description": "Button for the user to confirm that they have Signal for Android"
},
"installFollowUs": {
"message": "<a $a_params$>Follow us</a> for updates about multi-device support for iOS.",
"placeholders": {
"a_params": {
"content": "$1",
"example": "href='http://example.com'"
}
}
},
"installAndroidInstructions": {
2016-04-08 20:54:18 +00:00
"message": "Open Signal on your phone and navigate to Settings > Linked devices. Tap the button to add a new device, then scan the code above."
},
"installConnecting": {
"message": "Connecting...",
"description": "Displayed when waiting for the QR Code"
},
"installConnectionFailed": {
"message": "Failed to connect to server.",
"description": "Displayed when we can't connect to the server."
},
"installGeneratingKeys": {
"message": "Generating Keys"
},
"installSyncingGroupsAndContacts": {
"message": "Syncing groups and contacts"
},
"installComputerName": {
"message": "This computer's name will be",
"description": "Text displayed before the input where the user can enter the name for this device."
},
"installLinkingWithNumber": {
"message": "Linking with",
"description": "Text displayed before the phone number that the user is in the process of linking with"
},
"installFinalButton": {
"message": "Looking good",
"description": "The final button for the install process, after the user has entered a name for their device"
},
"installTooManyDevices": {
"message": "Sorry, you have too many devices linked already. Try removing some."
},
"settings": {
"message": "Settings",
"description": "Menu item and header for global settings"
},
2016-09-23 12:12:07 +00:00
"theme": {
"message": "Theme",
"description": "Header for theme settings"
},
"notifications": {
"message": "Notifications",
"description": "Header for notification settings"
},
"notificationSettingsDialog": {
"message": "When messages arrive, display notifications that reveal:",
"description": "Explain the purpose of the notification settings"
},
"disableNotifications": {
"message": "Disable notifications",
"description": "Label for disabling notifications"
},
"nameAndMessage": {
"message": "Both sender name and message",
"description": "Label for setting notifications to display name and message text"
},
"noNameOrMessage": {
"message": "Neither name nor message",
"description": "Label for setting notifications to display no name and no message text"
},
"nameOnly": {
"message": "Only sender name",
"description": "Label for setting notifications to display sender name only"
},
"newMessage": {
"message": "New Message",
"description": "Displayed in notifications for only 1 message"
},
"newMessages": {
"message": "New Messages",
"description": "Displayed in notifications for multiple messages"
},
"restartSignal": {
"message": "Restart Signal",
"description": "Menu item for restarting the program."
},
"messageNotSent": {
"message": "Message not sent.",
"description": "Informational label, appears on messages that failed to send"
},
"someRecipientsFailed": {
"message": "Some recipients failed.",
"description": "When you send to multiple recipients via a group, and the message went to some recipients but not others."
},
"showMore": {
"message": "Details",
"description": "Displays the details of a key change"
},
"showLess": {
"message": "Hide details",
"description": "Hides the details of a key change"
},
"learnMore": {
"message": "Learn more about verifying safety numbers",
2016-10-28 06:13:22 +00:00
"description": "Text that links to a support article on verifying safety numbers"
},
"expiredWarning": {
"message": "This version of Signal Desktop has expired. Please upgrade to the latest version to continue messaging.",
"description": "Warning notification that this version of the app has expired"
},
"androidMessageLengthWarning": {
"message": "Android clients will only receive the first 2000 characters of this message.",
"description": "Warning that long messages could not get received completely by Android clients."
},
"upgrade": {
"message": "Upgrade",
"description": "Label text for button to upgrade the app to the latest version"
},
"mediaMessage": {
"message": "Media message",
"description": "Description of a message that has an attachment and no text, displayed in the conversation list as a preview."
},
"unregisteredUser": {
"message": "Number is not registered",
"description": "Error message displayed when sending to an unregistered user."
},
"sync": {
"message": "Contacts",
"description": "Label for contact and group sync settings"
},
"syncExplanation": {
"message": "Import all Signal groups and contacts from your mobile device.",
"description": "Explanatory text for sync settings"
},
"lastSynced": {
"message": "Last import at",
"description": "Label for date and time of last sync operation"
},
"syncNow": {
"message": "Import now",
"description": "Label for a button that syncs contacts and groups from your phone"
},
"syncing": {
"message": "Importing...",
"description": "Label for a disabled sync button while sync is in progress."
},
"syncFailed": {
"message": "Import failed. Make sure your computer and your phone are connected to the internet.",
"description": "Informational text displayed if a sync operation times out."
},
"timestamp_s": {
"description": "Brief timestamp for messages sent less than a minute ago. Displayed in the conversation list and message bubble.",
"message": "now"
},
"timestamp_m": {
"description": "Brief timestamp for messages sent about one minute ago. Displayed in the conversation list and message bubble.",
"message": "1 minute"
},
"timestamp_h": {
"description": "Brief timestamp for messages sent about one minute ago. Displayed in the conversation list and message bubble.",
"message": "1 hour"
},
"timestampFormat_M": {
"description": "Timestamp format string for displaying month and day (but not the year) of a date within the current year, ex: use 'MMM D' for 'Aug 8', or 'D MMM' for '8 Aug'.",
"message": "MMM D"
},
"unblockToSend": {
"message": "Unblock this contact to send a message.",
"description": "Brief message shown when trying to message a blocked number"
2016-09-27 06:15:20 +00:00
},
"youChangedTheTimer": {
"message": "You set the timer to $time$.",
"description": "Message displayed when you change the message expiration timer in a conversation.",
"placeholders": {
"time": {
"content": "$1",
"example": "10m"
}
}
},
"theyChangedTheTimer": {
2016-09-27 06:15:20 +00:00
"message": "$name$ set the timer to $time$.",
"description": "Message displayed when someone else changes the message expiration timer in a conversation.",
2016-09-27 06:15:20 +00:00
"placeholders": {
"name": {
"content": "$1",
"example": "Bob"
},
"time": {
"content": "$2",
"example": "10m"
}
}
},
"timerOption_0_seconds": {
"message": "off",
"description": "Label for option to turn off message expiration in the timer menu"
},
"timerOption_5_seconds": {
"message": "5 seconds",
"description": "Label for a selectable option in the message expiration timer menu"
},
"timerOption_10_seconds": {
"message": "10 seconds",
"description": "Label for a selectable option in the message expiration timer menu"
},
"timerOption_30_seconds": {
"message": "30 seconds",
"description": "Label for a selectable option in the message expiration timer menu"
},
"timerOption_1_day": {
"message": "1 day",
"description": "Label for a selectable option in the message expiration timer menu"
},
"timerOption_1_week": {
"message": "1 week",
"description": "Label for a selectable option in the message expiration timer menu"
},
"disappearingMessages": {
"message": "Disappearing messages",
"description": "Conversation menu option to enable disappearing messages"
},
"timerOption_0_seconds_abbreviated": {
"message": "off",
2016-10-08 02:24:17 +00:00
"description": "Short format indicating current timer setting in the conversation list snippet"
},
"timerOption_5_seconds_abbreviated": {
"message": "5s",
2016-10-08 02:24:17 +00:00
"description": "Very short format indicating current timer setting in the conversation header"
},
"timerOption_10_seconds_abbreviated": {
"message": "10s",
2016-10-08 02:24:17 +00:00
"description": "Very short format indicating current timer setting in the conversation header"
},
"timerOption_30_seconds_abbreviated": {
"message": "30s",
2016-10-08 02:24:17 +00:00
"description": "Very short format indicating current timer setting in the conversation header"
},
"timerOption_1_minute_abbreviated": {
"message": "1m",
2016-10-08 02:24:17 +00:00
"description": "Very short format indicating current timer setting in the conversation header"
},
"timerOption_5_minutes_abbreviated": {
"message": "5m",
2016-10-08 02:24:17 +00:00
"description": "Very short format indicating current timer setting in the conversation header"
},
"timerOption_30_minutes_abbreviated": {
"message": "30m",
2016-10-08 02:24:17 +00:00
"description": "Very short format indicating current timer setting in the conversation header"
},
"timerOption_1_hour_abbreviated": {
"message": "1h",
2016-10-08 02:24:17 +00:00
"description": "Very short format indicating current timer setting in the conversation header"
},
"timerOption_6_hours_abbreviated": {
"message": "6h",
2016-10-08 02:24:17 +00:00
"description": "Very short format indicating current timer setting in the conversation header"
},
"timerOption_12_hours_abbreviated": {
"message": "12h",
2016-10-08 02:24:17 +00:00
"description": "Very short format indicating current timer setting in the conversation header"
},
"timerOption_1_day_abbreviated": {
"message": "1d",
2016-10-08 02:24:17 +00:00
"description": "Very short format indicating current timer setting in the conversation header"
},
"timerOption_1_week_abbreviated": {
"message": "1w",
2016-10-08 02:24:17 +00:00
"description": "Very short format indicating current timer setting in the conversation header"
},
"timerSetTo": {
"message": "Timer set to $time$",
"description": "Displayed in the conversation list when the timer is updated.",
"placeholders": {
"time": {
"content": "$1",
"example": "1w"
}
}
},
"audioNotificationDescription": {
"message": "Play audio notification",
"description": "Description for audio notification setting"
},
"keychanged": {
"message": "Your safety number with $name$ has changed. Click to show.",
"description": "",
"placeholders": {
"name": {
"content": "$1",
"example": "John"
}
}
},
"yourSafetyNumberWith": {
"message": "Your safety number with $name$:",
"description": "Heading for safety number view",
"placeholders": {
"name": {
"content": "$1",
"example": "John"
}
}
},
"themeAndroidDark": {
"message": "Android (dark)",
"description": "Label text for dark Android theme"
},
"newContact": {
"message": "Click to create new contact",
"description": ""
},
"newPhoneNumber": {
"message": "Enter a phone number to add a contact.",
"description": "Placeholder for adding a new number to a contact"
},
"invalidNumberError": {
"message": "Invalid number",
"description": "When a person inputs a number that is invalid"
},
"unlinkedWarning": {
"message": "Relink Signal Desktop to your mobile device to continue messaging."
},
"unlinked": {
"message": "Unlinked"
},
"relink": {
"message": "Relink"
},
"autoUpdateNewVersionTitle": {
"message": "Signal update available"
},
"autoUpdateNewVersionMessage": {
"message": "There is a new version of Signal available."
},
"autoUpdateNewVersionInstructions": {
"message": "Press Restart to apply the updates."
},
"autoUpdateRestartButtonLabel": {
"message": "Restart"
},
"autoUpdateLaterButtonLabel": {
"message": "Later"
}
2015-12-14 23:10:49 +00:00
}