/** * elFinder translation template * use this file to create new translation * submit new translation via https://github.com/Studio-42/elFinder/issues * or make a pull request */ /** * XXXXX translation * @author Translator Name * @version 201x-xx-xx */ (function(root, factory) { if (typeof define === 'function' && define.amd) { define(['elfinder'], factory); } else if (typeof exports !== 'undefined') { module.exports = factory(require('elfinder')); } else { factory(root.elFinder); } }(this, function(elFinder) { elFinder.prototype.i18.REPLACE_WITH_xx_OR_xx_YY_LANG_CODE = { translator : 'Translator name <translator@email.tld>', language : 'Language of translation in your language', direction : 'ltr', dateFormat : 'M d, Y h:i A', // will show like: Mar 13, 2012 05:27 PM fancyDateFormat : '$1 h:i A', // will show like: Today 12:25 PM nonameDateFormat : 'ymd-His', // noname upload will show like: 120513-172700 messages : { /********************************** errors **********************************/ 'error' : 'Error', 'errUnknown' : 'Unknown error.', 'errUnknownCmd' : 'Unknown command.', 'errJqui' : 'Invalid jQuery UI configuration. Selectable, draggable and droppable components must be included.', 'errNode' : 'elFinder requires DOM Element to be created.', 'errURL' : 'Invalid elFinder configuration! URL option is not set.', 'errAccess' : 'Access denied.', 'errConnect' : 'Unable to connect to backend.', 'errAbort' : 'Connection aborted.', 'errTimeout' : 'Connection timeout.', 'errNotFound' : 'Backend not found.', 'errResponse' : 'Invalid backend response.', 'errConf' : 'Invalid backend configuration.', 'errJSON' : 'PHP JSON module not installed.', 'errNoVolumes' : 'Readable volumes not available.', 'errCmdParams' : 'Invalid parameters for command "$1".', 'errDataNotJSON' : 'Data is not JSON.', 'errDataEmpty' : 'Data is empty.', 'errCmdReq' : 'Backend request requires command name.', 'errOpen' : 'Unable to open "$1".', 'errNotFolder' : 'Object is not a folder.', 'errNotFile' : 'Object is not a file.', 'errRead' : 'Unable to read "$1".', 'errWrite' : 'Unable to write into "$1".', 'errPerm' : 'Permission denied.', 'errLocked' : '"$1" is locked and can not be renamed, moved or removed.', 'errExists' : 'Item named "$1" already exists.', 'errInvName' : 'Invalid file name.', 'errInvDirname' : 'Invalid folder name.', // from v2.1.24 added 12.4.2017 'errFolderNotFound' : 'Folder not found.', 'errFileNotFound' : 'File not found.', 'errTrgFolderNotFound' : 'Target folder "$1" not found.', 'errPopup' : 'Browser prevented opening popup window. To open file enable it in browser options.', 'errMkdir' : 'Unable to create folder "$1".', 'errMkfile' : 'Unable to create file "$1".', 'errRename' : 'Unable to rename "$1".', 'errCopyFrom' : 'Copying files from volume "$1" not allowed.', 'errCopyTo' : 'Copying files to volume "$1" not allowed.', 'errMkOutLink' : 'Unable to create a link to outside the volume root.', // from v2.1 added 03.10.2015 'errUpload' : 'Upload error.', // old name - errUploadCommon 'errUploadFile' : 'Unable to upload "$1".', // old name - errUpload 'errUploadNoFiles' : 'No files found for upload.', 'errUploadTotalSize' : 'Data exceeds the maximum allowed size.', // old name - errMaxSize 'errUploadFileSize' : 'File exceeds maximum allowed size.', // old name - errFileMaxSize 'errUploadMime' : 'File type not allowed.', 'errUploadTransfer' : '"$1" transfer error.', 'errUploadTemp' : 'Unable to make temporary file for upload.', // from v2.1 added 26.09.2015 'errNotReplace' : 'Object "$1" already exists at this location and can not be replaced by object with another type.', // new 'errReplace' : 'Unable to replace "$1".', 'errSave' : 'Unable to save "$1".', 'errCopy' : 'Unable to copy "$1".', 'errMove' : 'Unable to move "$1".', 'errCopyInItself' : 'Unable to copy "$1" into itself.', 'errRm' : 'Unable to remove "$1".', 'errTrash' : 'Unable into trash.', // from v2.1.24 added 30.4.2017 'errRmSrc' : 'Unable remove source file(s).', 'errExtract' : 'Unable to extract files from "$1".', 'errArchive' : 'Unable to create archive.', 'errArcType' : 'Unsupported archive type.', 'errNoArchive' : 'File is not archive or has unsupported archive type.', 'errCmdNoSupport' : 'Backend does not support this command.', 'errReplByChild' : 'The folder "$1" can\'t be replaced by an item it contains.', 'errArcSymlinks' : 'For security reason denied to unpack archives contains symlinks or files with not allowed names.', // edited 24.06.2012 'errArcMaxSize' : 'Archive files exceeds maximum allowed size.', 'errResize' : 'Unable to resize "$1".', 'errResizeDegree' : 'Invalid rotate degree.', // added 7.3.2013 'errResizeRotate' : 'Unable to rotate image.', // added 7.3.2013 'errResizeSize' : 'Invalid image size.', // added 7.3.2013 'errResizeNoChange' : 'Image size not changed.', // added 7.3.2013 'errUsupportType' : 'Unsupported file type.', 'errNotUTF8Content' : 'File "$1" is not in UTF-8 and cannot be edited.', // added 9.11.2011 'errNetMount' : 'Unable to mount "$1".', // added 17.04.2012 'errNetMountNoDriver' : 'Unsupported protocol.', // added 17.04.2012 'errNetMountFailed' : 'Mount failed.', // added 17.04.2012 'errNetMountHostReq' : 'Host required.', // added 18.04.2012 'errSessionExpires' : 'Your session has expired due to inactivity.', 'errCreatingTempDir' : 'Unable to create temporary directory: "$1"', 'errFtpDownloadFile' : 'Unable to download file from FTP: "$1"', 'errFtpUploadFile' : 'Unable to upload file to FTP: "$1"', 'errFtpMkdir' : 'Unable to create remote directory on FTP: "$1"', 'errArchiveExec' : 'Error while archiving files: "$1"', 'errExtractExec' : 'Error while extracting files: "$1"', 'errNetUnMount' : 'Unable to unmount.', // from v2.1 added 30.04.2012 'errConvUTF8' : 'Not convertible to UTF-8', // from v2.1 added 08.04.2014 'errFolderUpload' : 'Try the modern browser, If you\'d like to upload the folder.', // from v2.1 added 26.6.2015 'errSearchTimeout' : 'Timed out while searching "$1". Search result is partial.', // from v2.1 added 12.1.2016 'errReauthRequire' : 'Re-authorization is required.', // from v2.1.10 added 24.3.2016 'errMaxTargets' : 'Max number of selectable items is $1.', // from v2.1.17 added 17.10.2016 'errRestore' : 'Unable to restore from the trash. Can\'t identify the restore destination.', // from v2.1.24 added 3.5.2017 'errEditorNotFound' : 'Editor not found to this file type.', // from v2.1.25 added 23.5.2017 'errServerError' : 'Error occurred on the server side.', // from v2.1.25 added 16.6.2017 'errEmpty' : 'Unable to empty folder "$1".', // from v2.1.25 added 22.6.2017 'moreErrors' : 'There are $1 more errors.', // from v2.1.44 added 9.12.2018 'errMaxMkdirs' : 'You can create up to $1 folders at one time.', // from v2.1.58 added 20.6.2021 /******************************* commands names ********************************/ 'cmdarchive' : 'Create archive', 'cmdback' : 'Back', 'cmdcopy' : 'Copy', 'cmdcut' : 'Cut', 'cmddownload' : 'Download', 'cmdduplicate' : 'Duplicate', 'cmdedit' : 'Edit file', 'cmdextract' : 'Extract files from archive', 'cmdforward' : 'Forward', 'cmdgetfile' : 'Select files', 'cmdhelp' : 'About this software', 'cmdhome' : 'Root', 'cmdinfo' : 'Get info', 'cmdmkdir' : 'New folder', 'cmdmkdirin' : 'Into New Folder', // from v2.1.7 added 19.2.2016 'cmdmkfile' : 'New file', 'cmdopen' : 'Open', 'cmdpaste' : 'Paste', 'cmdquicklook' : 'Preview', 'cmdreload' : 'Reload', 'cmdrename' : 'Rename', 'cmdrm' : 'Delete', 'cmdtrash' : 'Into trash', //from v2.1.24 added 29.4.2017 'cmdrestore' : 'Restore', //from v2.1.24 added 3.5.2017 'cmdsearch' : 'Find files', 'cmdup' : 'Go to parent folder', 'cmdupload' : 'Upload files', 'cmdview' : 'View', 'cmdresize' : 'Resize & Rotate', 'cmdsort' : 'Sort', 'cmdnetmount' : 'Mount network volume', // added 18.04.2012 'cmdnetunmount': 'Unmount', // from v2.1 added 30.04.2012 'cmdplaces' : 'To Places', // added 28.12.2014 'cmdchmod' : 'Change mode', // from v2.1 added 20.6.2015 'cmdopendir' : 'Open a folder', // from v2.1 added 13.1.2016 'cmdcolwidth' : 'Reset column width', // from v2.1.13 added 12.06.2016 'cmdfullscreen': 'Full Screen', // from v2.1.15 added 03.08.2016 'cmdmove' : 'Move', // from v2.1.15 added 21.08.2016 'cmdempty' : 'Empty the folder', // from v2.1.25 added 22.06.2017 'cmdundo' : 'Undo', // from v2.1.27 added 31.07.2017 'cmdredo' : 'Redo', // from v2.1.27 added 31.07.2017 'cmdpreference': 'Preferences', // from v2.1.27 added 03.08.2017 'cmdselectall' : 'Select all', // from v2.1.28 added 15.08.2017 'cmdselectnone': 'Select none', // from v2.1.28 added 15.08.2017 'cmdselectinvert': 'Invert selection', // from v2.1.28 added 15.08.2017 'cmdopennew' : 'Open in new window', // from v2.1.38 added 3.4.2018 'cmdhide' : 'Hide (Preference)', // from v2.1.41 added 24.7.2018 /*********************************** buttons ***********************************/ 'btnClose' : 'Close', 'btnSave' : 'Save', 'btnRm' : 'Remove', 'btnApply' : 'Apply', 'btnCancel' : 'Cancel', 'btnNo' : 'No', 'btnYes' : 'Yes', 'btnDiscard': 'Discard changes', 'btnMount' : 'Mount', // added 18.04.2012 'btnApprove': 'Goto $1 & approve', // from v2.1 added 26.04.2012 'btnUnmount': 'Unmount', // from v2.1 added 30.04.2012 'btnConv' : 'Convert', // from v2.1 added 08.04.2014 'btnCwd' : 'Here', // from v2.1 added 22.5.2015 'btnVolume' : 'Volume', // from v2.1 added 22.5.2015 'btnAll' : 'All', // from v2.1 added 22.5.2015 'btnMime' : 'MIME Type', // from v2.1 added 22.5.2015 'btnFileName':'Filename', // from v2.1 added 22.5.2015 'btnSaveClose': 'Save & Close', // from v2.1 added 12.6.2015 'btnBackup' : 'Backup', // fromv2.1 added 28.11.2015 'btnRename' : 'Rename', // from v2.1.24 added 6.4.2017 'btnRenameAll' : 'Rename(All)', // from v2.1.24 added 6.4.2017 'btnPrevious' : 'Prev ($1/$2)', // from v2.1.24 added 11.5.2017 'btnNext' : 'Next ($1/$2)', // from v2.1.24 added 11.5.2017 'btnSaveAs' : 'Save As', // from v2.1.25 added 24.5.2017 /******************************** notifications ********************************/ 'ntfopen' : 'Open folder', 'ntffile' : 'Open file', 'ntfreload' : 'Reload folder content', 'ntfmkdir' : 'Creating folder', 'ntfmkfile' : 'Creating files', 'ntfrm' : 'Delete items', 'ntfcopy' : 'Copy items', 'ntfmove' : 'Move items', 'ntfprepare' : 'Checking existing items', 'ntfrename' : 'Rename files', 'ntfupload' : 'Uploading files', 'ntfdownload' : 'Downloading files', 'ntfsave' : 'Save files', 'ntfarchive' : 'Creating archive', 'ntfextract' : 'Extracting files from archive', 'ntfsearch' : 'Searching files', 'ntfresize' : 'Resizing images', 'ntfsmth' : 'Doing something', 'ntfloadimg' : 'Loading image', 'ntfnetmount' : 'Mounting network volume', // added 18.04.2012 'ntfnetunmount': 'Unmounting network volume', // from v2.1 added 30.04.2012 'ntfdim' : 'Acquiring image dimension', // added 20.05.2013 'ntfreaddir' : 'Reading folder infomation', // from v2.1 added 01.07.2013 'ntfurl' : 'Getting URL of link', // from v2.1 added 11.03.2014 'ntfchmod' : 'Changing file mode', // from v2.1 added 20.6.2015 'ntfpreupload': 'Verifying upload file name', // from v2.1 added 31.11.2015 'ntfzipdl' : 'Creating a file for download', // from v2.1.7 added 23.1.2016 'ntfparents' : 'Getting path infomation', // from v2.1.17 added 2.11.2016 'ntfchunkmerge': 'Processing the uploaded file', // from v2.1.17 added 2.11.2016 'ntftrash' : 'Doing throw in the trash', // from v2.1.24 added 2.5.2017 'ntfrestore' : 'Doing restore from the trash', // from v2.1.24 added 3.5.2017 'ntfchkdir' : 'Checking destination folder', // from v2.1.24 added 3.5.2017 'ntfundo' : 'Undoing previous operation', // from v2.1.27 added 31.07.2017 'ntfredo' : 'Redoing previous undone', // from v2.1.27 added 31.07.2017 'ntfchkcontent' : 'Checking contents', // from v2.1.41 added 3.8.2018 /*********************************** volumes *********************************/ 'volume_Trash' : 'Trash', //from v2.1.24 added 29.4.2017 /************************************ dates **********************************/ 'dateUnknown' : 'unknown', 'Today' : 'Today', 'Yesterday' : 'Yesterday', 'msJan' : 'Jan', 'msFeb' : 'Feb', 'msMar' : 'Mar', 'msApr' : 'Apr', 'msMay' : 'May', 'msJun' : 'Jun', 'msJul' : 'Jul', 'msAug' : 'Aug', 'msSep' : 'Sep', 'msOct' : 'Oct', 'msNov' : 'Nov', 'msDec' : 'Dec', 'January' : 'January', 'February' : 'February', 'March' : 'March', 'April' : 'April', 'May' : 'May', 'June' : 'June', 'July' : 'July', 'August' : 'August', 'September' : 'September', 'October' : 'October', 'November' : 'November', 'December' : 'December', 'Sunday' : 'Sunday', 'Monday' : 'Monday', 'Tuesday' : 'Tuesday', 'Wednesday' : 'Wednesday', 'Thursday' : 'Thursday', 'Friday' : 'Friday', 'Saturday' : 'Saturday', 'Sun' : 'Sun', 'Mon' : 'Mon', 'Tue' : 'Tue', 'Wed' : 'Wed', 'Thu' : 'Thu', 'Fri' : 'Fri', 'Sat' : 'Sat', /******************************** sort variants ********************************/ 'sortname' : 'by name', 'sortkind' : 'by kind', 'sortsize' : 'by size', 'sortdate' : 'by date', 'sortFoldersFirst' : 'Folders first', 'sortperm' : 'by permission', // from v2.1.13 added 13.06.2016 'sortmode' : 'by mode', // from v2.1.13 added 13.06.2016 'sortowner' : 'by owner', // from v2.1.13 added 13.06.2016 'sortgroup' : 'by group', // from v2.1.13 added 13.06.2016 'sortAlsoTreeview' : 'Also Treeview', // from v2.1.15 added 01.08.2016 /********************************** new items **********************************/ 'untitled file.txt' : 'NewFile.txt', // added 10.11.2015 'untitled folder' : 'NewFolder', // added 10.11.2015 'Archive' : 'NewArchive', // from v2.1 added 10.11.2015 'untitled file' : 'NewFile.$1', // from v2.1.41 added 6.8.2018 'extentionfile' : '$1: File', // from v2.1.41 added 6.8.2018 'extentiontype' : '$1: $2', // from v2.1.43 added 17.10.2018 /********************************** messages **********************************/ 'confirmReq' : 'Confirmation required', 'confirmRm' : 'Are you sure you want to permanently remove items?
This cannot be undone!', 'confirmRepl' : 'Replace old file with new one? (If it contains folders, it will be merged. To backup and replace, select Backup.)', 'confirmRest' : 'Replace existing item with the item in trash?', // fromv2.1.24 added 5.5.2017 'confirmConvUTF8' : 'Not in UTF-8
Convert to UTF-8?
Contents become UTF-8 by saving after conversion.', // from v2.1 added 08.04.2014 'confirmNonUTF8' : 'Character encoding of this file couldn\'t be detected. It need to temporarily convert to UTF-8 for editting.
Please select character encoding of this file.', // from v2.1.19 added 28.11.2016 'confirmNotSave' : 'It has been modified.
Losing work if you do not save changes.', // from v2.1 added 15.7.2015 'confirmTrash' : 'Are you sure you want to move items to trash bin?', //from v2.1.24 added 29.4.2017 'confirmMove' : 'Are you sure you want to move items to "$1"?', //from v2.1.50 added 27.7.2019 'apllyAll' : 'Apply to all', 'name' : 'Name', 'size' : 'Size', 'perms' : 'Permissions', 'modify' : 'Modified', 'kind' : 'Kind', 'read' : 'read', 'write' : 'write', 'noaccess' : 'no access', 'and' : 'and', 'unknown' : 'unknown', 'selectall' : 'Select all items', 'selectfiles' : 'Select item(s)', 'selectffile' : 'Select first item', 'selectlfile' : 'Select last item', 'viewlist' : 'List view', 'viewicons' : 'Icons view', 'viewSmall' : 'Small icons', // from v2.1.39 added 22.5.2018 'viewMedium' : 'Medium icons', // from v2.1.39 added 22.5.2018 'viewLarge' : 'Large icons', // from v2.1.39 added 22.5.2018 'viewExtraLarge' : 'Extra large icons', // from v2.1.39 added 22.5.2018 'places' : 'Places', 'calc' : 'Calculate', 'path' : 'Path', 'aliasfor' : 'Alias for', 'locked' : 'Locked', 'dim' : 'Dimensions', 'files' : 'Files', 'folders' : 'Folders', 'items' : 'Items', 'yes' : 'yes', 'no' : 'no', 'link' : 'Link', 'searcresult' : 'Search results', 'selected' : 'selected items', 'about' : 'About', 'shortcuts' : 'Shortcuts', 'help' : 'Help', 'webfm' : 'Web file manager', 'ver' : 'Version', 'protocolver' : 'protocol version', 'homepage' : 'Project home', 'docs' : 'Documentation', 'github' : 'Fork us on GitHub', 'twitter' : 'Follow us on Twitter', 'facebook' : 'Join us on Facebook', 'team' : 'Team', 'chiefdev' : 'chief developer', 'developer' : 'developer', 'contributor' : 'contributor', 'maintainer' : 'maintainer', 'translator' : 'translator', 'icons' : 'Icons', 'dontforget' : 'and don\'t forget to take your towel', 'shortcutsof' : 'Shortcuts disabled', 'dropFiles' : 'Drop files here', 'or' : 'or', 'selectForUpload' : 'Select files', 'moveFiles' : 'Move items', 'copyFiles' : 'Copy items', 'restoreFiles' : 'Restore items', // from v2.1.24 added 5.5.2017 'rmFromPlaces' : 'Remove from places', 'aspectRatio' : 'Aspect ratio', 'scale' : 'Scale', 'width' : 'Width', 'height' : 'Height', 'resize' : 'Resize', 'crop' : 'Crop', 'rotate' : 'Rotate', 'rotate-cw' : 'Rotate 90 degrees CW', 'rotate-ccw' : 'Rotate 90 degrees CCW', 'degree' : '°', 'netMountDialogTitle' : 'Mount network volume', // added 18.04.2012 'protocol' : 'Protocol', // added 18.04.2012 'host' : 'Host', // added 18.04.2012 'port' : 'Port', // added 18.04.2012 'user' : 'User', // added 18.04.2012 'pass' : 'Password', // added 18.04.2012 'confirmUnmount' : 'Are you unmount $1?', // from v2.1 added 30.04.2012 'dropFilesBrowser': 'Drop or Paste files from browser', // from v2.1 added 30.05.2012 'dropPasteFiles' : 'Drop files, Paste URLs or images(clipboard) here', // from v2.1 added 07.04.2014 'encoding' : 'Encoding', // from v2.1 added 19.12.2014 'locale' : 'Locale', // from v2.1 added 19.12.2014 'searchTarget' : 'Target: $1', // from v2.1 added 22.5.2015 'searchMime' : 'Search by input MIME Type', // from v2.1 added 22.5.2015 'owner' : 'Owner', // from v2.1 added 20.6.2015 'group' : 'Group', // from v2.1 added 20.6.2015 'other' : 'Other', // from v2.1 added 20.6.2015 'execute' : 'Execute', // from v2.1 added 20.6.2015 'perm' : 'Permission', // from v2.1 added 20.6.2015 'mode' : 'Mode', // from v2.1 added 20.6.2015 'emptyFolder' : 'Folder is empty', // from v2.1.6 added 30.12.2015 'emptyFolderDrop' : 'Folder is empty\\A Drop to add items', // from v2.1.6 added 30.12.2015 'emptyFolderLTap' : 'Folder is empty\\A Long tap to add items', // from v2.1.6 added 30.12.2015 'quality' : 'Quality', // from v2.1.6 added 5.1.2016 'autoSync' : 'Auto sync', // from v2.1.6 added 10.1.2016 'moveUp' : 'Move up', // from v2.1.6 added 18.1.2016 'getLink' : 'Get URL link', // from v2.1.7 added 9.2.2016 'selectedItems' : 'Selected items ($1)', // from v2.1.7 added 2.19.2016 'folderId' : 'Folder ID', // from v2.1.10 added 3.25.2016 'offlineAccess' : 'Allow offline access', // from v2.1.10 added 3.25.2016 'reAuth' : 'To re-authenticate', // from v2.1.10 added 3.25.2016 'nowLoading' : 'Now loading...', // from v2.1.12 added 4.26.2016 'openMulti' : 'Open multiple files', // from v2.1.12 added 5.14.2016 'openMultiConfirm': 'You are trying to open the $1 files. Are you sure you want to open in browser?', // from v2.1.12 added 5.14.2016 'emptySearch' : 'Search results is empty in search target.', // from v2.1.12 added 5.16.2016 'editingFile' : 'It is editing a file.', // from v2.1.13 added 6.3.2016 'hasSelected' : 'You have selected $1 items.', // from v2.1.13 added 6.3.2016 'hasClipboard' : 'You have $1 items in the clipboard.', // from v2.1.13 added 6.3.2016 'incSearchOnly' : 'Incremental search is only from the current view.', // from v2.1.13 added 6.30.2016 'reinstate' : 'Reinstate', // from v2.1.15 added 3.8.2016 'complete' : '$1 complete', // from v2.1.15 added 21.8.2016 'contextmenu' : 'Context menu', // from v2.1.15 added 9.9.2016 'pageTurning' : 'Page turning', // from v2.1.15 added 10.9.2016 'volumeRoots' : 'Volume roots', // from v2.1.16 added 16.9.2016 'reset' : 'Reset', // from v2.1.16 added 1.10.2016 'bgcolor' : 'Background color', // from v2.1.16 added 1.10.2016 'colorPicker' : 'Color picker', // from v2.1.16 added 1.10.2016 '8pxgrid' : '8px Grid', // from v2.1.16 added 4.10.2016 'enabled' : 'Enabled', // from v2.1.16 added 4.10.2016 'disabled' : 'Disabled', // from v2.1.16 added 4.10.2016 'emptyIncSearch' : 'Search results is empty in current view.\\APress [Enter] to expand search target.', // from v2.1.16 added 5.10.2016 'emptyLetSearch' : 'First letter search results is empty in current view.', // from v2.1.23 added 24.3.2017 'textLabel' : 'Text label', // from v2.1.17 added 13.10.2016 'minsLeft' : '$1 mins left', // from v2.1.17 added 13.11.2016 'openAsEncoding' : 'Reopen with selected encoding', // from v2.1.19 added 2.12.2016 'saveAsEncoding' : 'Save with the selected encoding', // from v2.1.19 added 2.12.2016 'selectFolder' : 'Select folder', // from v2.1.20 added 13.12.2016 'firstLetterSearch': 'First letter search', // from v2.1.23 added 24.3.2017 'presets' : 'Presets', // from v2.1.25 added 26.5.2017 'tooManyToTrash' : 'It\'s too many items so it can\'t into trash.', // from v2.1.25 added 9.6.2017 'TextArea' : 'TextArea', // from v2.1.25 added 14.6.2017 'folderToEmpty' : 'Empty the folder "$1".', // from v2.1.25 added 22.6.2017 'filderIsEmpty' : 'There are no items in a folder "$1".', // from v2.1.25 added 22.6.2017 'preference' : 'Preference', // from v2.1.26 added 28.6.2017 'language' : 'Language', // from v2.1.26 added 28.6.2017 'clearBrowserData': 'Initialize the settings saved in this browser', // from v2.1.26 added 28.6.2017 'toolbarPref' : 'Toolbar settings', // from v2.1.27 added 2.8.2017 'charsLeft' : '... $1 chars left.', // from v2.1.29 added 30.8.2017 'linesLeft' : '... $1 lines left.', // from v2.1.52 added 16.1.2020 'sum' : 'Sum', // from v2.1.29 added 28.9.2017 'roughFileSize' : 'Rough file size', // from v2.1.30 added 2.11.2017 'autoFocusDialog' : 'Focus on the element of dialog with mouseover', // from v2.1.30 added 2.11.2017 'select' : 'Select', // from v2.1.30 added 23.11.2017 'selectAction' : 'Action when select file', // from v2.1.30 added 23.11.2017 'useStoredEditor' : 'Open with the editor used last time', // from v2.1.30 added 23.11.2017 'selectinvert' : 'Invert selection', // from v2.1.30 added 25.11.2017 'renameMultiple' : 'Are you sure you want to rename $1 selected items like $2?
This cannot be undone!', // from v2.1.31 added 4.12.2017 'batchRename' : 'Batch rename', // from v2.1.31 added 8.12.2017 'plusNumber' : '+ Number', // from v2.1.31 added 8.12.2017 'asPrefix' : 'Add prefix', // from v2.1.31 added 8.12.2017 'asSuffix' : 'Add suffix', // from v2.1.31 added 8.12.2017 'changeExtention' : 'Change extention', // from v2.1.31 added 8.12.2017 'columnPref' : 'Columns settings (List view)', // from v2.1.32 added 6.2.2018 'reflectOnImmediate' : 'All changes will reflect immediately to the archive.', // from v2.1.33 added 2.3.2018 'reflectOnUnmount' : 'Any changes will not reflect until un-mount this volume.', // from v2.1.33 added 2.3.2018 'unmountChildren' : 'The following volume(s) mounted on this volume also unmounted. Are you sure to unmount it?', // from v2.1.33 added 5.3.2018 'selectionInfo' : 'Selection Info', // from v2.1.33 added 7.3.2018 'hashChecker' : 'Algorithms to show the file hash', // from v2.1.33 added 10.3.2018 'infoItems' : 'Info Items (Selection Info Panel)', // from v2.1.38 added 28.3.2018 'pressAgainToExit': 'Press again to exit.', // from v2.1.38 added 1.4.2018 'toolbar' : 'Toolbar', // from v2.1.38 added 4.4.2018 'workspace' : 'Work Space', // from v2.1.38 added 4.4.2018 'dialog' : 'Dialog', // from v2.1.38 added 4.4.2018 'all' : 'All', // from v2.1.38 added 4.4.2018 'iconSize' : 'Icon Size (Icons view)', // from v2.1.39 added 7.5.2018 'editorMaximized' : 'Open the maximized editor window', // from v2.1.40 added 30.6.2018 'editorConvNoApi' : 'Because conversion by API is not currently available, please convert on the website.', //from v2.1.40 added 8.7.2018 'editorConvNeedUpload' : 'After conversion, you must be upload with the item URL or a downloaded file to save the converted file.', //from v2.1.40 added 8.7.2018 'convertOn' : 'Convert on the site of $1', // from v2.1.40 added 10.7.2018 'integrations' : 'Integrations', // from v2.1.40 added 11.7.2018 'integrationWith' : 'This elFinder has the following external services integrated. Please check the terms of use, privacy policy, etc. before using it.', // from v2.1.40 added 11.7.2018 'showHidden' : 'Show hidden items', // from v2.1.41 added 24.7.2018 'hideHidden' : 'Hide hidden items', // from v2.1.41 added 24.7.2018 'toggleHidden' : 'Show/Hide hidden items', // from v2.1.41 added 24.7.2018 'makefileTypes' : 'File types to enable with "New file"', // from v2.1.41 added 7.8.2018 'typeOfTextfile' : 'Type of the Text file', // from v2.1.41 added 7.8.2018 'add' : 'Add', // from v2.1.41 added 7.8.2018 'theme' : 'Theme', // from v2.1.43 added 19.10.2018 'default' : 'Default', // from v2.1.43 added 19.10.2018 'description' : 'Description', // from v2.1.43 added 19.10.2018 'website' : 'Website', // from v2.1.43 added 19.10.2018 'author' : 'Author', // from v2.1.43 added 19.10.2018 'email' : 'Email', // from v2.1.43 added 19.10.2018 'license' : 'License', // from v2.1.43 added 19.10.2018 'exportToSave' : 'This item can\'t be saved. To avoid losing the edits you need to export to your PC.', // from v2.1.44 added 1.12.2018 'dblclickToSelect': 'Double click on the file to select it.', // from v2.1.47 added 22.1.2019 'useFullscreen' : 'Use fullscreen mode', // from v2.1.47 added 19.2.2019 /********************************** mimetypes **********************************/ 'kindUnknown' : 'Unknown', 'kindRoot' : 'Volume Root', // from v2.1.16 added 16.10.2016 'kindFolder' : 'Folder', 'kindSelects' : 'Selections', // from v2.1.29 added 29.8.2017 'kindAlias' : 'Alias', 'kindAliasBroken' : 'Broken alias', // applications 'kindApp' : 'Application', 'kindPostscript' : 'Postscript document', 'kindMsOffice' : 'Microsoft Office document', 'kindMsWord' : 'Microsoft Word document', 'kindMsExcel' : 'Microsoft Excel document', 'kindMsPP' : 'Microsoft Powerpoint presentation', 'kindOO' : 'Open Office document', 'kindAppFlash' : 'Flash application', 'kindPDF' : 'Portable Document Format (PDF)', 'kindTorrent' : 'Bittorrent file', 'kind7z' : '7z archive', 'kindTAR' : 'TAR archive', 'kindGZIP' : 'GZIP archive', 'kindBZIP' : 'BZIP archive', 'kindXZ' : 'XZ archive', 'kindZIP' : 'ZIP archive', 'kindRAR' : 'RAR archive', 'kindJAR' : 'Java JAR file', 'kindTTF' : 'True Type font', 'kindOTF' : 'Open Type font', 'kindRPM' : 'RPM package', // fonts 'kindFont' : 'Font', 'kindSFNT' : 'SFNT font', 'kindEOT' : 'Embedded Open Type font', 'kindWOFF' : 'Web Open Font Format', 'kindWOFF2' : 'Web Open Font Format 2', // texts 'kindText' : 'Text document', 'kindTextPlain' : 'Plain text', 'kindPHP' : 'PHP source', 'kindCSS' : 'Cascading style sheet', 'kindHTML' : 'HTML document', 'kindJS' : 'Javascript source', 'kindRTF' : 'Rich Text Format', 'kindC' : 'C source', 'kindCHeader' : 'C header source', 'kindCPP' : 'C++ source', 'kindCPPHeader' : 'C++ header source', 'kindShell' : 'Unix shell script', 'kindPython' : 'Python source', 'kindJava' : 'Java source', 'kindRuby' : 'Ruby source', 'kindPerl' : 'Perl script', 'kindSQL' : 'SQL source', 'kindXML' : 'XML document', 'kindAWK' : 'AWK source', 'kindCSV' : 'Comma separated values', 'kindDOCBOOK' : 'Docbook XML document', 'kindMarkdown' : 'Markdown text', // added 20.7.2015 // images 'kindImage' : 'Image', 'kindBMP' : 'BMP image', 'kindJPEG' : 'JPEG image', 'kindGIF' : 'GIF Image', 'kindPNG' : 'PNG Image', 'kindTIFF' : 'TIFF image', 'kindTGA' : 'TGA image', 'kindPSD' : 'Adobe Photoshop image', 'kindXBITMAP' : 'X bitmap image', 'kindPXM' : 'Pixelmator image', // media 'kindAudio' : 'Audio media', 'kindAudioMPEG' : 'MPEG audio', 'kindAudioMPEG4' : 'MPEG-4 audio', 'kindAudioMIDI' : 'MIDI audio', 'kindAudioOGG' : 'Ogg Vorbis audio', 'kindAudioWAV' : 'WAV audio', 'AudioPlaylist' : 'MP3 playlist', 'kindVideo' : 'Video media', 'kindVideoDV' : 'DV movie', 'kindVideoMPEG' : 'MPEG movie', 'kindVideoMPEG4' : 'MPEG-4 movie', 'kindVideoAVI' : 'AVI movie', 'kindVideoMOV' : 'Quick Time movie', 'kindVideoWM' : 'Windows Media movie', 'kindVideoFlash' : 'Flash movie', 'kindVideoMKV' : 'Matroska movie', 'kindVideoOGG' : 'Ogg movie' } }; })); ( function () { 'use strict'; window.InlineShortcodeView_vc_gallery = window.InlineShortcodeView.extend({ render: function () { var model_id = this.model.get( 'id' ); window.InlineShortcodeView_vc_gallery.__super__.render.call( this ); vc.frame_window.vc_iframe.addActivity( function () { this.vc_iframe.vc_gallery( model_id ); }); return this; }, parentChanged: function () { window.InlineShortcodeView_vc_gallery.__super__.parentChanged.call( this ); vc.frame_window.vc_iframe.vc_gallery( this.model.get( 'id' ) ); } }); })(); ( function () { 'use strict'; window.InlineShortcodeView_vc_masonry_media_grid = window.InlineShortcodeView_vc_basic_grid.extend(); })(); Private Key Generation in Ledger Wallet: How the Hardware Device Creates and Protects Your Keys – DahChen Design

Private Key Generation in Ledger Wallet: How the Hardware Device Creates and Protects Your Keys

A common misconception about cryptocurrency wallets is that the application itself generates and stores private keys. Users familiar with traditional software wallets often expect that when they create an account, the app on their phone or computer performs the cryptographic work. Ledger Wallet operates on a fundamentally different principle: private keys are never created or held by the application. Instead, the Ledger hardware device performs key generation in an isolated environment, keeping the secrets off any internet-connected system. This architectural choice is the reason why compromising the app, the device’s operating system, or even the computer running the application cannot expose the private keys themselves.

The implications of this design extend beyond mere convenience. When a user initiates a transaction through Ledger Wallet, the application prepares the transaction details but cannot sign them without the hardware device’s approval. The device receives the transaction, the user verifies the recipient and amount on the device’s screen, and only then does the hardware perform the cryptographic signing. This separation means that malware on a computer, a phishing website, or a compromised application cannot intercept keys or forge transactions without physical access to the hardware. Understanding how this protection works requires examining the complete flow: how keys originate, where they reside, and why the application’s role is deliberately constrained.

Ledger hardware device showing secure key generation environment isolated from internet-connected systems

How private keys originate on the Ledger device

When a user sets up a Ledger device for the first time, the hardware generates a twenty-four-word Secret Recovery Phrase through a random number generation process that occurs entirely on the device. This phrase is the root seed from which all cryptocurrency keys are derived. The device’s firmware uses a hardware-based random number generator (RNG) that is designed to produce cryptographically secure randomness, meeting the standards required for generating secrets that will protect real assets. This process happens before the device is ever connected to a computer or phone running Ledger Wallet.

The Secret Recovery Phrase itself is displayed only on the device’s screen during initial setup, never transmitted to Ledger servers, the application, or any external system. The user is instructed to write the phrase on paper and store it in a secure location. This offline recording is intentional: because the phrase is the master seed, keeping it completely offline and separate from any internet-connected device prevents a compromised computer from harvesting it. The twenty-four words encode approximately 264 bits of entropy, sufficient to make brute-force attacks computationally infeasible while remaining practical for a human to record and verify.

From this Secret Recovery Phrase, the Ledger device derives all cryptocurrency addresses and their corresponding private keys using the BIP32 hierarchical deterministic (HD) wallet standard. This means that every address associated with a user’s accounts can be regenerated from the recovery phrase alone, and the device can recreate the entire wallet structure if necessary. However, the device never exposes the individual private keys. Instead, the hardware stores the master seed internally and uses it to perform signing operations when transactions require approval. This is a crucial distinction: the device contains the seed, not the application.

The application’s limited view of private key storage

Ledger Wallet never receives, stores, or has access to private keys in any form. The application’s role is to prepare transactions, display account balances, show transaction history, and present information fetched from blockchain APIs. When a user connects their Ledger device to a computer or phone running Ledger Wallet, the application communicates with the hardware over a USB or Bluetooth connection, but this communication is limited to specific, well-defined commands. The app can request that the device derive a public address for display purposes, but it receives only the public address, not the private key.

This architectural constraint is enforced at multiple levels. The Ledger device firmware includes a secure boot process that verifies its own integrity before executing, making it difficult for an attacker to modify the software that manages keys. The communication protocol between the application and the device includes cryptographic verification, so the device can confirm that commands are being sent from authentic software. When the user initiates a transaction, Ledger Wallet sends the transaction details to the device, which then displays the critical information (recipient address, amount, fees) on its own screen for the user to verify before signing.

Public addresses, by contrast, are stored in the Ledger Wallet application so that users can see their balances, receive funds, and manage multiple accounts. These addresses are derived from the device and can be shared without risk because they are mathematically one-way: knowing a public address provides no information that could generate the corresponding private key. The application also stores transaction history, account labels, and portfolio data, all of which can be safely maintained on an internet-connected device because none of this information can be used to steal funds or forge transactions.

Why separation prevents key theft at the application level

The most common attack vectors against cryptocurrency wallets involve compromising the application through malware, phishing, or supply chain attacks. If private keys were stored in the app or derived within the app, a compromised application could harvest them immediately. A keylogger, screen scraper, or packet sniffer could potentially capture secrets during or after generation. Because Ledger Wallet never handles private keys, these attacks fail. A compromised application might trick the user into approving a malicious transaction, but it cannot steal keys or create unauthorized transactions without the user’s explicit approval on the Ledger device itself.

Consider a practical scenario: a user unknowingly installs a malicious version of Ledger Wallet or the application becomes compromised through a vulnerability. The attacker gains full access to the application’s memory, files, and network communications. An attacker with this level of access could see the user’s public addresses, transaction history, and current balances. However, the attacker still cannot spend any funds because doing so requires a transaction signature generated by the Ledger hardware device. The private keys remain secure in the isolated hardware environment, completely outside the compromised software’s reach.

This protection extends to the operating system level. Even if an attacker gains administrative access to a Windows, macOS, Linux, Android, or iOS system running Ledger Wallet, the private keys stored on the Ledger device remain protected. The hardware enforces a security boundary that the operating system cannot cross. The only way to sign a transaction is through the legitimate Ledger device firmware, which requires the user to physically interact with the hardware (pressing a button to confirm) and verify the transaction details on the device’s screen. An attacker would need physical access to the device to exploit this security model, which is a fundamentally different threat than compromising software alone.

The Secret Recovery Phrase and offline security

The Secret Recovery Phrase serves a secondary function beyond the initial setup process: it is the backup mechanism that allows recovery if the Ledger device is lost, damaged, or stolen. Because the phrase can regenerate the entire wallet, it is the single most critical secret a user must protect. The design philosophy is to keep this phrase completely offline during normal use and to request it only when the user is performing a recovery action on a new device. Ledger Wallet and Ledger servers will never ask for this phrase during normal operation, and users are explicitly warned that anyone who asks for it is attempting theft.

The offline nature of the Secret Recovery Phrase recovery is intentional. When a user enters the recovery phrase into a new Ledger device, the device itself performs the verification and key derivation. The application never sees the phrase. This is why users are instructed to download ledger wallet app only from official Ledger sources and to verify the authenticity of their device before using it for recovery. A phishing site or malicious device claiming to need the recovery phrase is a red flag. The legitimate recovery process requires only physical interaction with an authentic Ledger device and entry of the phrase directly into that hardware.

Users who lose access to their Ledger device but have safely stored their Secret Recovery Phrase can recover all funds by obtaining a new Ledger device and entering the phrase during setup. The new device will regenerate the same keys, the same addresses, and access to the same accounts. This recovery mechanism is powerful precisely because it is not dependent on Ledger servers, cloud backups, or any online service. It is also why the phrase must be stored with extreme care and never typed into a computer connected to the internet, photographed, or shared with anyone.

Hardware-based verification and clear signing

When a user approves a transaction, Ledger Wallet displays the transaction details on the computer or phone screen, but the Ledger device displays the critical information independently on its own screen. This is an important security distinction: the hardware device has its own display, which is connected only to the device’s processor and secure storage. The application cannot manipulate what appears on the device’s screen. A user who sees a different recipient address on the device screen than what the application showed has detected a potential attack or misconfiguration and should not proceed.

This process is called clear signing: the user can read and verify the actual transaction parameters on the hardware device before authorizing the signature. The device’s firmware will not sign a transaction that the user did not explicitly approve by pressing the physical button. An attacker who compromised the application could display fake transaction details on the phone or computer, but the device would still show the real transaction parameters. The user verifies the correct information on the device and approves it, creating a signature that applies only to the authentic transaction.

The signing process itself uses public-key cryptography. The Ledger device contains the private key, which remains isolated. When the application requests a signature for a transaction, the device performs the cryptographic computation using its private key and returns only the signature itself. The application can then broadcast this signed transaction to the blockchain. The private key never leaves the device. This is why even a perfectly executed attack against the application, the network, or the blockchain API cannot generate valid signatures without the device’s cooperation.

Genuine Check and authentication of the device

Ledger includes a Genuine Check feature in Ledger Wallet that allows users to verify that their device is an authentic Ledger product. This is important because counterfeit devices exist in the market, and a fake device could be designed to leak the recovery phrase or private keys to an attacker. The Genuine Check process communicates with Ledger’s servers to verify the device’s authenticity using cryptographic proof. While this check does involve an online connection, it only authenticates the device hardware and does not expose any keys or sensitive account information.

The threat model that Genuine Check addresses is distinct from app-level compromise. A counterfeit device might appear to work like a legitimate Ledger but could have modified firmware that transmits secrets during setup or signing. By verifying the device is authentic before trusting it with recovery phrase entry or large transactions, users reduce the risk of being targeted by a sophisticated supply chain attack. This check is most important during initial setup and before recovering a wallet from a Secret Recovery Phrase on a new device.

Users should be aware that Genuine Check is complementary to, not a substitute for, offline security practices. A counterfeit device that passes Genuine Check would indicate a sophisticated forgery that bypassed Ledger’s authentication mechanisms. A device purchased from an official retailer or directly from Ledger is far less likely to be counterfeit than one obtained from an unknown third-party seller. The hardware security model remains valid as long as the physical device is authentic and has not been physically tampered with during shipping or storage.

The transactional workflow from application to device signature

Understanding the complete workflow illustrates why private key storage on the Ledger device prevents application-level theft. A user creating a transaction in Ledger Wallet begins by specifying the destination address, amount, and desired transaction fee. The application constructs the transaction data but does not sign it. Instead, the application sends the transaction to the connected Ledger device for signing approval. The device receives this unsigned transaction, decodes the transaction parameters, and displays them on its own screen: the recipient address, the amount, and any other relevant details.

The user verifies that the transaction details match their intent. They confirm that the recipient address is correct, the amount is what they intended to send, and the fee is acceptable. Only after this verification does the user press the physical button on the Ledger device to authorize the signature. The device’s secure processor then uses the private key to generate a digital signature for the transaction. This signature is returned to the application, which combines it with the unsigned transaction to create a complete, signed transaction ready for broadcast to the blockchain.

Broadcasting the signed transaction is the final step, and it can happen immediately or be delayed at the user’s discretion. The application sends the signed transaction to the blockchain network, which verifies the signature using the public key (which is publicly known and cannot be kept secret). The blockchain accepts the transaction because the signature is cryptographically valid and matches the public key associated with the sending address. Throughout this entire process, the private key remained on the Ledger device. The application handled the unsigned transaction data, the network transmitted the signed transaction, and the blockchain verified the signature—but none of these steps gave anyone access to the actual private key.

Why this architecture is resistant to common attacks

The separation of key generation and storage on the hardware device from the application’s transaction preparation functions creates multiple security boundaries that each independently prevent common attack vectors. Malware running on a user’s computer cannot intercept the private key because the key never passes through the operating system or any internet-connected component. A man-in-the-middle attacker cannot modify a transaction signature because the signature is generated by the hardware device after the user has verified the transaction on the device’s screen.

Phishing attacks that trick users into visiting malicious websites or installing fake applications cannot steal private keys because the keys never exist in the application. A user who visits a convincing phishing site designed to look like Ledger Wallet might enter their recovery phrase into the fake site, which would be a critical mistake—but this is why users are trained never to enter the phrase except during legitimate device setup or recovery. The recovery phrase itself is the key to preventing this attack: by keeping it offline and recognizing that no legitimate Ledger process asks for it during normal use, users can detect and avoid phishing attempts.

Supply chain attacks that attempt to compromise Ledger software distributed through official channels are mitigated by the fact that even compromised application code cannot access private keys. An attacker could modify the application to display false transaction details, attempt to trick the user into approving a malicious transaction, or harvest public address data—but the hardware device provides independent verification. When the user looks at the device screen and sees a different transaction than what the application displayed, they will not approve it. The hardware security boundary prevents the attack from succeeding.

Practical implications for users managing cryptocurrency accounts

For users evaluating cryptocurrency wallet security, the Ledger architecture demonstrates why hardware separation matters in practice. The private key storage on the Ledger device means that users can safely run Ledger Wallet on devices that may have security concerns: an older computer, a phone with few security updates, or a system that has been exposed to potentially malicious software. The worst-case scenario from app-level compromise is that an attacker learns the public addresses and transaction history, which is a significant privacy concern but does not result in theft of funds.

This does not mean hardware wallets are invulnerable. Users can still make mistakes: entering recovery phrases into phishing sites, confirming fraudulent transactions on the device screen without reading carefully, or losing the recovery phrase entirely. Physical attacks on the Ledger device, while difficult, remain theoretically possible for sophisticated attackers. Users should not assume that the hardware device requires no additional precautions: securing the device against loss or theft, maintaining a safely stored recovery phrase backup, and being vigilant about transaction verification remain essential practices.

The most practical implication is that users managing substantial cryptocurrency balances can operate with a security model that compartmentalizes risk. The internet-connected application and computer can be assumed to be potentially compromised without losing the ability to protect private keys. Recovery and backup can be managed entirely offline. Transactions can be verified on independent hardware before being approved for signing. This design does not achieve perfect security—nothing does—but it raises the bar for attacks significantly compared to applications that generate and store keys locally.

Frequently asked questions

Does Ledger Wallet store my private keys when I connect my hardware device?

No. Ledger Wallet never receives, stores, or has access to private keys. The application communicates with your Ledger device to prepare and sign transactions, but the actual private keys remain on the hardware device at all times. Even if your computer or phone becomes compromised, the private keys are protected because they exist only on the isolated hardware.

What happens if someone gains access to my computer running Ledger Wallet?

An attacker with access to your computer can see your public addresses, transaction history, and account balances through Ledger Wallet. However, they cannot spend your funds or create valid transactions because doing so requires signing with your private key, which only your Ledger device can do. They would need physical access to your device and would have to successfully trick you into approving a fraudulent transaction on the device screen.

Where is my Secret Recovery Phrase stored, and why should I keep it offline?

Your Secret Recovery Phrase is generated and stored only on your Ledger device during initial setup. It is never transmitted to Ledger servers or the Ledger Wallet application. You should write it down on paper and store it in a secure physical location because it can regenerate your entire wallet if your device is lost. Keeping it offline prevents anyone who compromises your computer or phone from obtaining the phrase and recovering your accounts on a different device.

2026-09-15T23:27:52+08:00