Update sandman_zh_TW.ts

Update Traditional Chinese Translation
This commit is contained in:
Tragic Life 2024-10-20 16:28:50 +08:00 committed by GitHub
parent 37281006f9
commit 1d981009b7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 21 additions and 21 deletions

View File

@ -2114,7 +2114,7 @@ Note: The update check is often behind the latest GitHub release to ensure that
<message>
<location filename="Windows/OptionsForce.cpp" line="151"/>
<source>Document</source>
<translation type="unfinished"></translation>
<translation></translation>
</message>
<message>
<location filename="Windows/OptionsForce.cpp" line="265"/>
@ -2133,23 +2133,23 @@ Note: The update check is often behind the latest GitHub release to ensure that
<message>
<location filename="Windows/OptionsForce.cpp" line="327"/>
<source>Select Document Directory</source>
<translation type="unfinished"></translation>
<translation></translation>
</message>
<message>
<location filename="Windows/OptionsForce.cpp" line="331"/>
<source>Please enter Document File Extension.</source>
<translation type="unfinished"></translation>
<translation></translation>
</message>
<message>
<location filename="Windows/OptionsForce.cpp" line="341"/>
<source>For security reasons it it not permitted to create entirely wildcard BreakoutDocument presets.</source>
<oldsource>For security reasons it it not permitted to create entierly wildcard BreakoutDocument presets.</oldsource>
<translation type="unfinished"></translation>
<translation></translation>
</message>
<message>
<location filename="Windows/OptionsForce.cpp" line="351"/>
<source>For security reasons the specified extension %1 should not be broken out.</source>
<translation type="unfinished"></translation>
<translation> %1 </translation>
</message>
<message>
<location filename="Windows/OptionsForce.cpp" line="408"/>
@ -2963,7 +2963,7 @@ Full path: %4</source>
<message>
<location filename="Windows/RecoveryWindow.cpp" line="246"/>
<source>No Files selected!</source>
<translation type="unfinished"></translation>
<translation></translation>
</message>
<message>
<location filename="Windows/RecoveryWindow.cpp" line="250"/>
@ -7344,7 +7344,7 @@ If you are a great patreaon supporter already, sandboxie can check online for an
<message>
<location filename="Forms/ExtractDialog.ui" line="82"/>
<source>Import without encryption</source>
<translation type="unfinished"></translation>
<translation></translation>
</message>
</context>
<context>
@ -7861,7 +7861,7 @@ If you are a great patreaon supporter already, sandboxie can check online for an
<message>
<location filename="Forms/OptionsWindow.ui" line="2380"/>
<source>&lt;b&gt;&lt;font color=&apos;red&apos;&gt;SECURITY ADVISORY&lt;/font&gt;:&lt;/b&gt; Using &lt;a href=&quot;sbie://docs/breakoutfolder&quot;&gt;BreakoutFolder&lt;/a&gt; and/or &lt;a href=&quot;sbie://docs/breakoutprocess&quot;&gt;BreakoutProcess&lt;/a&gt; in combination with Open[File/Pipe]Path directives can compromise security, as can the use of &lt;a href=&quot;sbie://docs/breakoutdocument&quot;&gt;BreakoutDocument&lt;/a&gt; allowing any * or insecure (*.exe;*.dll;*.ocx;*.cmd;*.bat;*.lnk;*.pif;*.url;*.ps1;etc) extensions. Please review the security section for each option in the documentation before use.</source>
<translation>&lt;b&gt;&lt;font color=&apos;red&apos;&gt;&lt;/font&gt;: &lt;/b&gt;使 &lt;a href=&quot;sbie://docs/breakoutfolder&quot;&gt;BreakoutFolder&lt;/a&gt; / &lt;a href=&quot; sbie://docs/breakoutprocess&quot;&gt;BreakoutProcess&lt;/a&gt; Open[File/Pipe]Path 使使 &lt;a href=&quot;sbie://docs/breakoutdocument&quot;&gt;BreakoutDocument&lt; /a &gt; * (*.exe;*.dll;*.ocx;*.cmd;*.bat;*.lnk;*.pif;*.url;*.ps1;etc) 使</translation>
<translation>&lt;b&gt;&lt;font color=&apos;red&apos;&gt;&lt;/font&gt;: &lt;/b&gt;使 &lt;a href=&quot;sbie://docs/breakoutfolder&quot;&gt;&lt;/a&gt; / &lt;a href=&quot; sbie://docs/breakoutprocess&quot;&gt;&lt;/a&gt; [/]使使 &lt;a href=&quot;sbie://docs/breakoutdocument&quot;&gt;&lt; /a &gt; * (*.exe;*.dll;*.ocx;*.cmd;*.bat;*.lnk;*.pif;*.url;*.ps1;etc) 使</translation>
</message>
<message>
<location filename="Forms/OptionsWindow.ui" line="2400"/>
@ -8076,7 +8076,7 @@ If you are a great patreaon supporter already, sandboxie can check online for an
This is done to prevent rogue processes inside the sandbox from creating a renamed copy of themselves and accessing protected resources. Another exploit vector is the injection of a library into an authorized process to get access to everything it is allowed to access. Using Host Image Protection, this can be prevented by blocking applications (installed on the host) running inside a sandbox from loading libraries from the sandbox itself.</source>
<oldsource>Sandboxies resource access rules often discriminate against program binaries located inside the sandbox. OpenFilePath and OpenKeyPath work only for application binaries located on the host natively. In order to define a rule without this restriction, OpenPipePath or OpenConfPath must be used. Likewise, all Closed(File|Key|Ipc)Path directives which are defined by negation e.g. ClosedFilePath=! iexplore.exe,C:Users* will be always closed for binaries located inside a sandbox. Both restriction policies can be disabled on the Access policies page.
This is done to prevent rogue processes inside the sandbox from creating a renamed copy of themselves and accessing protected resources. Another exploit vector is the injection of a library into an authorized process to get access to everything it is allowed to access. Using Host Image Protection, this can be prevented by blocking applications (installed on the host) running inside a sandbox from loading libraries from the sandbox itself.</oldsource>
<translation>Sandboxie () 使(||IPC)&apos;ClosedFilePath=! iexplore.exe,C:Users*&apos;
<translation>Sandboxie () 使(||IPC)&apos;ClosedFilePath=! iexplore.exe,C:Users*&apos;
使 () </translation>
</message>
<message>
@ -8206,7 +8206,7 @@ Partially checked: No groups will be added to the newly created sandboxed token.
</message>
<message>
<source>&lt;b&gt;&lt;font color=&apos;red&apos;&gt;SECURITY ADVISORY&lt;/font&gt;:&lt;/b&gt; Using &lt;a href=&quot;sbie://docs/breakoutfolder&quot;&gt;BreakoutFolder&lt;/a&gt; and/or &lt;a href=&quot;sbie://docs/breakoutprocess&quot;&gt;BreakoutProcess&lt;/a&gt; in combination with Open[File/Pipe]Path directives can compromise security. Please review the security section for each option in the documentation before use.</source>
<translation type="vanished">&lt;b&gt;&lt;font color=&apos;red&apos;&gt;&lt;/font&gt;:&lt;/b&gt; 使 &lt;a href=&quot;sbie://docs/breakoutfolder&quot;&gt;&lt;/a&gt; / &lt;a href=&quot; sbie://docs/breakoutprocess&quot;&gt;&lt;/a&gt; [/]使使</translation>
<translation type="vanished">&lt;b&gt;&lt;font color=&apos;red&apos;&gt;&lt;/font&gt;:&lt;/b&gt; 使 &lt;a href=&quot;sbie://docs/breakoutfolder&quot;&gt;&lt;/a&gt; / &lt;a href=&quot; sbie://docs/breakoutprocess&quot;&gt;&lt;/a&gt; [/]使使</translation>
</message>
<message>
<location filename="Forms/OptionsWindow.ui" line="2410"/>
@ -8249,7 +8249,7 @@ Partially checked: No groups will be added to the newly created sandboxed token.
<location filename="Forms/OptionsWindow.ui" line="2855"/>
<source>Configure which processes can access Files, Folders and Pipes.
&apos;Open&apos; access only applies to program binaries located outside the sandbox, you can use &apos;Open for All&apos; instead to make it apply to all programs, or change this behavior in the Policies tab.</source>
<translation>
<translation>
使</translation>
</message>
<message>
@ -8448,7 +8448,7 @@ To specify a process use &apos;$:program.exe&apos; as path.</source>
<message>
<location filename="Forms/OptionsWindow.ui" line="508"/>
<source>Allow sandboxed processes to open files protected by EFS</source>
<translation type="unfinished"></translation>
<translation> EFS () </translation>
</message>
<message>
<location filename="Forms/OptionsWindow.ui" line="819"/>
@ -8468,18 +8468,18 @@ To specify a process use &apos;$:program.exe&apos; as path.</source>
<message>
<location filename="Forms/OptionsWindow.ui" line="961"/>
<source>Open access to Proxy Configurations</source>
<translation type="unfinished"></translation>
<translation> Proxy </translation>
</message>
<message>
<location filename="Forms/OptionsWindow.ui" line="1281"/>
<source>File ACLs</source>
<translation type="unfinished"></translation>
<translation> (ACL)</translation>
</message>
<message>
<location filename="Forms/OptionsWindow.ui" line="1331"/>
<source>Use original Access Control Entries for boxed Files and Folders (for MSIServer enable exemptions)</source>
<oldsource>Use original Access Control Entries for boxed Files and Folders (for MSIServer enable excemptions)</oldsource>
<translation type="unfinished"></translation>
<translation>使 (Access Control Entries) ( MSIServer )</translation>
</message>
<message>
<location filename="Forms/OptionsWindow.ui" line="1896"/>
@ -8499,7 +8499,7 @@ To specify a process use &apos;$:program.exe&apos; as path.</source>
<message>
<location filename="Forms/OptionsWindow.ui" line="2373"/>
<source>Breakout Document</source>
<translation type="unfinished"></translation>
<translation></translation>
</message>
<message>
<location filename="Forms/OptionsWindow.ui" line="2942"/>
@ -8738,7 +8738,7 @@ The process match level has a higher priority than the specificity and describes
<message>
<location filename="Forms/OptionsWindow.ui" line="1950"/>
<source>Start the sandboxed RpcSs as a SYSTEM process (not recommended)</source>
<translation> RpcSs ()</translation>
<translation> RPC ()</translation>
</message>
<message>
<location filename="Forms/OptionsWindow.ui" line="1872"/>
@ -9036,7 +9036,7 @@ Note: Forced Programs and Force Folders settings for a sandbox do not apply to
<message>
<location filename="Forms/OptionsWindow.ui" line="5139"/>
<source>Pipe Trace</source>
<translation></translation>
<translation></translation>
</message>
<message>
<location filename="Forms/OptionsWindow.ui" line="5153"/>
@ -9259,7 +9259,7 @@ Please note that this values are currently user specific and saved globally for
<message>
<location filename="Forms/OptionsWindow.ui" line="1657"/>
<source>Limit restrictions</source>
<translation></translation>
<translation></translation>
</message>
<message>
<source>Leave it blank to disable the setting(Unit:KB)</source>
@ -10376,12 +10376,12 @@ Unlike the preview channel, it does not include untested, potentially breaking,
<message>
<location filename="Forms/SettingsWindow.ui" line="2266"/>
<source>This feature protects the sandbox by restricting access, preventing other users from accessing the folder. Ensure the root folder path contains the %USER% macro so that each user gets a dedicated sandbox folder.</source>
<translation type="unfinished"></translation>
<translation>使 %USER% 使</translation>
</message>
<message>
<location filename="Forms/SettingsWindow.ui" line="2269"/>
<source>Restrict box root folder access to the the user whom created that sandbox</source>
<translation type="unfinished"></translation>
<translation>使</translation>
</message>
<message>
<location filename="Forms/SettingsWindow.ui" line="2379"/>