User talk:1416006136
Comments on talk pages should be signed with "~~~~", which will be converted into your signature and a timestamp.
Note:Please talk in English or in Chinese.Update a Template
并不是什么大事，只是你能不能更新下Template:PreservedEnt:zh？原页面进行了一次大修，但恕我功底不行没法进行更新（） --Yakumo koishi (talk) 15:38, 24 Dec 2021 (UTC)
- 我现在更新了 Template:PreservedEnt:zh 页面。 --DarkKong (talk) 0:49, 25 Dec 2021 (UTC)
- Got it, thx --Yakumo koishi (talk) 1:07, 25 Dec 2021 (UTC)
翻译建议
先生您好，您在曾经地翻译中对 遮挡器（occluder）、位移（Displacement）、可见性分支区域（visleaf）等部分内容地翻译并不合适、有一定机翻的现象，请您翻译时仔细斟酌并现行更正。将感谢您从百忙中抽出的时间，望您知晓，谢谢！ --Coma (talk) 11:09, 2 Jul 2022 (UTC)
好的，我知道了。感谢您的建议！ --DarkKong (talk) 4:23, 7 Jul 2022 (UTC)
Translating articles
First I'd like to express my thanks for your contribution. I think certain practice in the translation can be debated, specifically, marking that the page is translated by someone on some date at the beginning of the article. Since the wiki is a community project, every user may contribute, and we already have the history saved by the server. I'm afraid the mark could discourage further updates and/or improvements from other users.
首先感谢阁下的贡献。本人认为文章翻译的一个做法有待商榷，具体来说是在文章开头标记某人某日翻译。维基乃由社区共同维护，每位用户都可以贡献，服务器自会留存历史记录。本人担忧这一标记会阻碍其他用户进一步更新或改进。
Not related, but I suggest both brush and solid should be translated to 固体.
另外，本人认为「brush」和「solid」都应翻译为「固体」。 --FloraC (talk) 14:36, 15 Jul 2022 (UTC)
- Ok, I got it. Thank you for your suggestions! I will adopt these suggestions. --DarkKong (talk) 17:50, 15 Jul 2022 (UTC)
Test
testing --大康 (talk) 19:25, 27 Jan 2023 (UTC)
About the edit for "Left 4 Dead 2/Script Functions/en".
您好！维基的华文词汇我不流利，请体谅。最新的编辑看起来将所用的 "<code>" 改成 "{{Code}}"。 这应该花了不少的时间，但是我认为编辑之后的颜色反差干扰了读者的专心能力，所以我只留了我觉得是不错的部分，希望可理解。以下是我在什么情况下留了"{{Code}}"：
- "Launch options".
- I/O 输入与输出。
- 描述里的函数。
- 如果排列不被逗号分开又在一条线里, 变量们的名字如果与写脚本有关联。
- 任何可运行的代码或命令。
以上的不是该跟的规则，只是我编辑的总结，未来我也可能会纠正自己的编辑。如果您对我的编辑有任何的问题，请随时提问。 — Orin (talk) 13:13, 19 Aug 2023
- 我觉得那是不错的主意。
我之前认为页面上全是<code>显得代码部分很难被分辨，所以我计划把代码部分的文字使用的<code>标签改为{{Code}}模板。
这固然花费了一些时间，但我是通过使用正则表达式来替换文本，所以工作量会少很多。原先的页面上有些使用<code>标签的文本在正文文本之间是没有空格的，所以我也顺便为它们添加了空格以隔开正文和代码，这也方便其他非英语读者将其复制到翻译器里进行翻译，同时也美观。
各种函数名称(列 Function 中的)确实可以不使用{{Code}}模板，这样看起来比较顺眼。
不过我认为 Signature 部分可以使用{{CodeBlock}}。例如：
| Function | Signature | Description |
|---|---|---|
__KeyValueFromInt__KeyValueFromFloat__KeyValueFromString__KeyValueFromVector
|
Sets an entity keyvalue from a specific data type. Returns true if successfully set, false if it the key does not exist.
This simply changes the value without executing any other code that may be needed for the entity to fully process the keyvalue, such as code for updating the entity's internal network state. This can create unexpected side effects on already-spawned entities such as visual changes being delayed for clients.  Tip:Use Netprops and update the keyvalue's corresponding prop instead, as this correctly updates the networking state and results in an immediate update. |
所以，在 Signature 中使用 {{CodeBlock}} 能够更好地区分代码。
I think that's a good idea.
I think all the codes on the page were used the tag <code>, which made it difficult to distinguish with the text and the code, so I planned to replace the tag <code> to the template {{Code}}. Certainly, it took some time, but I replaced them by using Regular Expression, so the workload was much less. There was no space between the code and the text in the previous revision. Therefore, I added spaces for them. This not only is useful for non-English readers to copy them to the translator to translate, but also looks good.
Various function names (in column Function) can indeed look more pleasing without using {{Code}} templates.
However, I think the column Signature can use {{CodeBlock}}. For example:
| Function | Signature | Description |
|---|---|---|
__KeyValueFromInt__KeyValueFromFloat__KeyValueFromString__KeyValueFromVector
|
Sets an entity keyvalue from a specific data type. Returns true if successfully set, false if it the key does not exist.
This simply changes the value without executing any other code that may be needed for the entity to fully process the keyvalue, such as code for updating the entity's internal network state. This can create unexpected side effects on already-spawned entities such as visual changes being delayed for clients. Tip:Use Netprops and update the keyvalue's corresponding prop instead, as this correctly updates the networking state and results in an immediate update. |
So using {{CodeBlock}} could distinguish the code better.
TF2 console command page broken?
Not sure if this was specifically your changes that did this, but your recent changes to Template:MultiPage appears to have maybe broken List of Team Fortress 2 console commands and variables; As far as I can tell, it was fine before this. --Adrmcr (talk) 15:37, 29 Aug 2023
Thank you!
I don't know if anyone has thanked you for this yet, but thank you for all the translation work you do! You're an absolute machine! --TF2CutContent (talk) 11:37, 27 Nov 2023
- It's a pleasure. I just have done some work to promote the new standard, and benefit more people. (Mainly because these pages are too unpleasant) --DarkKong (talk) 12:56, 27 Nov 2023
Ibfotsble template seems busred
Some stuff isn't working as of your autolang changes, like custom "dev" parameter text doesn't show up anymore (check HLMV++'s table, it should way ficool2 in the developer field). I think the issue stems from where you changed some "#default" entries used for switch statements over to "1=" for autolang. There's likely other stuff broken in the template now.
Edit: nevermind, I fixed it. I thought it was gonna be a harder issue to figure out but then I stumbled across the issue and fixed it. --TF2CutContent (talk) 5:17, 28 Nov 2023
- Well, I just replaced the #default to 1 simply, so some of the #default that shouldn't be replaced were replaced. Maybe I should add more matching criteria next time. --DarkKong (talk) 4:50, 29 Nov 2023
Your translation sign
I have often seen your translations, you constantly indicate yourself at the top of the article for everyone to see (when you have translated it), it looks strange and inappropriate. I think there is no need to do this. --NOUG4AT (talk) 20:32, 4 Jan 2024
- It's for certain that the sign isn't necessary, but due to various reasons I will add it to some of the pages I have translated. These reasons are too complex. Simply put, this is a habit of Chinese people to shows how contributions they have done. Of course, I will not add the sign to any other page that is not translated by me or is not Chinese. I am also trying not to add the sign if can. You can find that there are the signs that indicate who translated it in many translated pages in Chinese besides mine. This can be said to be a common phenomenon in the Chinese community. --DarkKong (talk) 4:39, 14 Feb 2024
Sidebar translation
Hello, I was wondering if you could help translate some of the sidebar strings into Chinese at the Valve Developer Community:Translators' noticeboard? --Wisdurm (talk) 17:41, 15 Jun 2024
- Of course I can, but I'm busy these days. I will do it later. --DarkKong (talk) 08:16, 20 June 2024 (PDT)
Autolang and int=1
Greetings. As I understand it, using {{Autolang|int=1 [... contents ...]}} allowed for previewing the translated /strings subpages.
But I discovered that in the case of {{Infobox game}}, while it did let me preview the translations indeed, it actually broke those translations on the pages. They were displaying only the eng names of the infobox fields.
That template was recently updated to use /strings and Russian and Croatian translations were added. I at first didn't add |int=1 when I was moving it from plain text to /strings, so everything worked (on pages). Then I remembered |int=1 was being added to other templates that day, and did the same. Did something go wrong?
At the moment I removed |int=1 from those strings so the preview doesn't work but pages do. Cvoxalury (talk) 02:41, 18 July 2024 (PDT)
- Actually
|int=1will take back to the previous translation method, which {{Autolang}} will change contents according to interface language instead of page language.
The function of previewing the translated /strings subpages is that the template will check if it is used on its own pages (the template page itself and the template's subpages) or other pages: if the template is used on its own pages, then the strings will change contents according to UI language; otherwise, it will do it according to page language. {{This is a/strings}} has achieved this.
If you want the function, you can add a simple criterion to determine whether int is 1 or 0:
In the case of {{Infobox game/strings}}: - In this example, we use an ifeq to determine whether the template is being used on its own page (return 1) or on other pages (return 0). If is is used on the template's pages, strings will change according to interface language and can be previewed by switching interface language. If not, strings will change according to language prefixes. —DarkKong (talk) 11:56, 18 July 2024 (PDT)
- This may be integrated into the Autolang template in the future. DarkKong (talk) 11:59, 18 July 2024 (PDT)
- Now I have finished the previewing function on {{Infobox game/strings}}. DarkKong (talk) 12:10, 18 July 2024 (PDT)
Changing the title to be in English
I was going through Category:Orphans to see if the lang prefixes are moved to their own category, while looking through the category i saw a title in Chinese and without a prefix. Can you change the title to be in English for this page CSGO VScript 范例? --N0one (talk) 10:05, 15 January 2025 (PST)