Improved Chinese translation#164
Conversation
* Replace the Chinese colon and parentheses with the English ones * Semantic improvement ...
Extensions/dnSpy.Debugger/dnSpy.Debugger/Properties/dnSpy.Debugger.Resources.zh-CN.resx
Outdated
Show resolved
Hide resolved
...iler/dnSpy.Decompiler.ILSpy.Core/Properties/dnSpy.Decompiler.ILSpy.Core.Resources.zh-CN.resx
Outdated
Show resolved
Hide resolved
Extensions/dnSpy.AsmEditor/Properties/dnSpy.AsmEditor.Resources.zh-CN.resx
Outdated
Show resolved
Hide resolved
Extensions/dnSpy.AsmEditor/Properties/dnSpy.AsmEditor.Resources.zh-CN.resx
Outdated
Show resolved
Hide resolved
* Replace Chinese punctuation with English punctuation
Extensions/dnSpy.AsmEditor/Properties/dnSpy.AsmEditor.Resources.zh-CN.resx
Outdated
Show resolved
Hide resolved
Extensions/dnSpy.AsmEditor/Properties/dnSpy.AsmEditor.Resources.zh-CN.resx
Outdated
Show resolved
Hide resolved
Extensions/dnSpy.AsmEditor/Properties/dnSpy.AsmEditor.Resources.zh-CN.resx
Outdated
Show resolved
Hide resolved
...nSpy.Debugger.DotNet.CorDebug/Properties/dnSpy.Debugger.DotNet.CorDebug.Resources.zh-CN.resx
Outdated
Show resolved
Hide resolved
...bugger/dnSpy.Debugger.DotNet.Mono/Properties/dnSpy.Debugger.DotNet.Mono.Resources.zh-CN.resx
Outdated
Show resolved
Hide resolved
Extensions/dnSpy.Debugger/dnSpy.Debugger/Properties/dnSpy.Debugger.Resources.zh-CN.resx
Outdated
Show resolved
Hide resolved
dnSpy/Roslyn/dnSpy.Roslyn/Properties/dnSpy.Roslyn.Resources.zh-CN.resx
Outdated
Show resolved
Hide resolved
UlyssesWu
left a comment
There was a problem hiding this comment.
Looks Good To Me
Thanks for your contribution @noisrev !
request merge @ElektroKill
...iler/dnSpy.Decompiler.ILSpy.Core/Properties/dnSpy.Decompiler.ILSpy.Core.Resources.zh-CN.resx
Outdated
Show resolved
Hide resolved
Extensions/dnSpy.AsmEditor/Properties/dnSpy.AsmEditor.Resources.zh-CN.resx
Show resolved
Hide resolved
| </data> | ||
| <data name="DecompilerSettings_DecompileAnonMethods" xml:space="preserve"> | ||
| <value>反编译匿名方法/lambda方法</value> | ||
| <value>反编译匿名方法和 lambda 方法</value> |
There was a problem hiding this comment.
There was a problem hiding this comment.
There was a problem hiding this comment.
那这里不应该是 Lambda 表达式和匿名函数吗
确实,我可能误解了他的意思(我以为他要去掉“匿名方法”)。Lambda后面如果要接一个词,更合理的应该是“表达式”。可能是因为原文只是lambdas(而不是lambda expressions),所以原来的翻译才会写成这样。至于“匿名方法”,由于原文就是methods,所以至少不能算错,但改成“函数”也不错。
Decompile anonymous methods/lambdas
| </data> | ||
| <data name="DecompilerSettings_MemberAddPrivateModifier" xml:space="preserve"> | ||
| <value>添加private标识符到类成员</value> | ||
| <value>为类成员添加 private 关键字</value> |
| </data> | ||
| <data name="DecompilerSettings_ShowTokensRvasOffsets" xml:space="preserve"> | ||
| <value>显示标记,RVA和文件偏移</value> | ||
| <value>显示标记,相对虚拟地址和文件偏移</value> |
There was a problem hiding this comment.
“标记”是个通用词,含义不明确,另外这里应该使用顿号分隔:
显示元数据标记、相对虚拟地址和文件偏移
| </data> | ||
| <data name="DecompilerSettings_TypeAddInternalModifier" xml:space="preserve"> | ||
| <value>添加internal标识符到类</value> | ||
| <value>为类添加 internal 关键字</value> |
Extensions/dnSpy.BamlDecompiler/Properties/dnSpy.BamlDecompiler.Resources.zh-CN.resx
Show resolved
Hide resolved
| </data> | ||
| <data name="DisassembleBAMLCommand" xml:space="preserve"> | ||
| <value>反汇编BAML</value> | ||
| <value>反汇编 BAML</value> |
| </data> | ||
| <data name="Error_IComponentConnectorConnectCannotBeParsed" xml:space="preserve"> | ||
| <value>类 '{0}' 有 IComponentConnector.Connect 方法,但无法解析。</value> | ||
| <value>目标类 '{0}' 存在 IComponentConnector.Connect 方法,但无法解析。</value> |
There was a problem hiding this comment.
反对,原文就是Class
Class '{0}' has IComponentConnector.Connect method, but cannot be parsed.
| </data> | ||
| <data name="Error_IStyleConnectorConnectCannotBeParsed" xml:space="preserve"> | ||
| <value>类 '{0}' 有 IStyleConnector.Connect 方法,但无法解析。</value> | ||
| <value>目标类 '{0}' 存在 IStyleConnector.Connect 方法,但无法解析。</value> |
| </data> | ||
| <data name="Error_UnknownConnectionId" xml:space="preserve"> | ||
| <value>未知连接 ID:{0}</value> | ||
| <value>未知的连接 ID: {0}</value> |
| </data> | ||
| <data name="AskDeleteAllBreakpoints" xml:space="preserve"> | ||
| <value>要删除所有的断点吗?</value> | ||
| <value>是否要删除所有的断点?</value> |
| </data> | ||
| <data name="Error_CantEvalWhenUnhandledExceptionHasOccurred" xml:space="preserve"> | ||
| <value>当未捕捉异常发生时无法计算</value> | ||
| <value>当未捕的捉异常发生时无法求值</value> |
| </data> | ||
| <data name="InvalidDateTime" xml:space="preserve"> | ||
| <value>值必须为DateTime</value> | ||
| <value>目标值必须为 DateTime</value> |
There was a problem hiding this comment.
直接翻译成“无效的 DateTime“就行了吧?这里表达的是数据格式错误,而不是使用了其他类型。
比如数据为:"2023.2.6",如果提示为“目标值必须为 DateTime”,会让用户一头雾水,他会觉得本来就已经是日期数据了,怎么还说不是呢?如果提示“无效的 DateTime“,用户就会觉得可能是分隔符错误,从而尝试使用"2023-2-6"或"2023/2/6"。其他的地方类似。
There was a problem hiding this comment.
直接翻译成“无效的 DateTime“就行了吧?
这个我倒没注意到,确实这样比较好理解
There was a problem hiding this comment.
直接翻译成“无效的 DateTime“就行了吧?
虽然这样看起来简单直白,但是描述的不够清晰。
还有很多相似的内容,总不能全都翻译成 无效的 xxx 吧。
譬如 InvalidBoolean、InvalidChar、InvalidString1 ......
其次,目标 这两个字可有可无,如有觉得不恰当我可以将它们删除掉
There was a problem hiding this comment.
考虑一个输入框只允许输入数字,当按下'a'键时,可能引发InvalidChar,此时如果提示:目标值必须为 Char,就是说'a'不是Char类型,但显然'a'就是Char,只是说在当前输入框是无效的
There was a problem hiding this comment.
其实上方就有这个 InvalidChar: 字符必须括在单引号 (')
在考虑到你说的这些之后,我认为就是 无效的 DateTime,请检查分隔符或格式是否拼写正确
在此基础上加多一条信息,这样既不会太单调,也能起到一个提示的效果。
如果没问题的话,其它地方我也会更改为类似的这种
There was a problem hiding this comment.
没必要添加额外信息
- 你并不能确定格式错误是什么原因,我说"2023.2.6"只是一个示例,如果是"year2035"这样,那就是完完全全的无效数据,并不是增加分隔符就能解决的
- 额外信息往往存在于Message属性中,不需要根据异常类型来添加额外信息
| </data> | ||
| <data name="UsesTreeNode" xml:space="preserve"> | ||
| <value>使用</value> | ||
| <value>使用于</value> |
There was a problem hiding this comment.
“使用”指的是正在分析的方法里用到了哪些其他方法,“使用于”听起来更像是“被使用”。我觉得之前的翻译没问题。
|
Thanks a lot for this contribution :p |
Improve the translation of Chinese