| Thread title | Replies | Last modified |
|---|---|---|
| Chinese language doesn't have italics | 1 | 00:58, 7 July 2011 |
| 啊，我有罪，分类的命名 | 3 | 04:31, 29 April 2011 |
| Span tags | 3 | 05:51, 22 April 2011 |
| Welcome to KDE UserBase/zh 沒必要吧 | 3 | 20:20, 18 March 2011 |
| 不要吐嘈我的翻译…… | 8 | 20:57, 12 March 2011 |
| Chinese translations | 3 | 21:26, 5 March 2011 |
That amendment started me thinking. There must be a number of such things that are important but language-specific. I wonder if it would be better to replace that change with a statement to the effect that some guidelines are not entirely applicable to specific languages, following it with a recommendation to add such things to the language-team pages, those linked from Translation_Workflow. (We also need to encourage more teams to form.) Thoughts?
原本我是用Category:桌面应用 (zh CN)，后来感觉太长，直接用Category:桌面 (zh CN)，因为就一个人在改，所以也没改掉 Category Translation 简体中文 to 正體中文，导致出现2个分类，我全去改成Category:桌面 (zh CN)了。
From time to time I've seen you remove span tags (sometimes other people, too). I asked Claus_chr to explain the tags, as I only vaguely understood them. This is what he said:
The reason for adding span tags is the following: Without them, klicking a link of the form Whatever on a translated page takes the user to the top of "Somepage/da" (assuming the user is Danish) rather than to the desired paragraph. The reason seems to be that the link is treated as SomePage/da#Paragraph, but on the translated page there is no paragraph named "Paragraph" - the name has been translated.
Without the span tags, each translator needs to translate the subpage part of the link to whatever the section title was translated to - this is particularly difficult, if that page haven't actually been translated yet :-)
Adding span tags also have great advantages to writers of original pages, as it makes this kind of link maintainable: Without them, if a writer wants to modify a section title, he should also search the whole UserBase for any possible subpage links to that title and modify them acordingly (and then translators needs to modify the corresponding translations) - more likely, however, he will forget and thus break all links to that section. Having span tags also means, that if we need to make larger changes to a page, we will at least be alerted to potential problems with pages linking to it, so that we can take appropriate actions.
As you can imagine I feel very strongly, that adding span tags is a Good Thing(TM), and that there would need to very good reasons indeed to remove them (I can't imagine what those reasons could be).
Hope that helps.
sorry, I don't quite get it... Could you show me some examples that you have added those span tags I removed?
My apologies. I wasn't working well yesterday. Every example I can see from your recent edits are fuzzy-bot span-tags, and not at all the things that I'm worried about. Again, I do apologise. I have too many things going on at the moment, and am over-tired :-(
你是yeeyan的人啊？我也有yeeyan帐号，就是没翻译过（套近乎 一个人翻译、修订、更新、迁移很累的（我在找借口 那么（喝口茶 加油吧（这是鼓励 我现在主要还在把旧的翻译迁移到到前的翻译插件上来，我个人页面那一堆_(zh_结尾的页面就是。
哈哈。我哪儿是什么yeeyan的人阿 我就是去年夏天没啥事儿做 然后去那儿翻译了点东西。
你那大多数翻译的都还不错的～吐槽？好吧。。。我感觉kde真的就是让咱翻译，一行一行的。。。
我会帮你忙的。。。虽然我很忙吧。。。我现在想法就是把一些翻译弄得更，怎么说呢，“行文流水”一些，就是连贯点，易理解点。。。
一会儿我看看你那“old style” section。
先写作业了，，回见～～
因为mediawiki原本不是这样的，userbase自己搞了个翻译插件，现在是一段一段的翻译，好处嘛就是方便同步，英文版出变动，中文版面过时的翻译段落就会标红，还有翻译数据统计神马的，坏处嘛……泪哗啦啦的流，所有之前的翻译全部手动复制粘贴弄进新的翻译插件上来。
对……比如EVA_(zh_CN)这种只是给大陆人用的，所以我也没弄英文页面，之前很随便，因为中文页面是人处理编辑的，现在不行了，我考虑移到我的个人页面下面。但是你的想法我估计没法做到吧，标红英文页面……要知道其它语种可是那么多，反正嘛，插件化有得有失，反正本来在这帮弄也没什么人，所以总体还是好处比较多。
很多东西没办法的，比如说简繁，最好的做法是zh.opensuse.org那种（我是那边的管理员），那边本身mediawiki的语言就是设定成zh，我开了简繁转换表，很方便，但是那边又不像这边有同步插件，英文那边变了，中文很难同步上。毕竟linux资料英文的比较全，所以基本都是从英文翻译过来。
You should talk to Qiii2006, who will help you to get started. Qiii2006 has worked alone for a long time, and his time is limited, so he would probably welcome some help, but please respect his wishes about priorities.
Meanwhile, you need to request a Translator Account, then read the Contributors' Help files.
KDE UserBase Wiki 