User talk:Karthikp

Jump to: navigation, search

Hi! The old rekonq manual - just delete everything that is out of date. Take care to keep the category statement, though. Don't worry about anything, as the versions are saved and can be recovered if anything is accidentally lost. --annew 19:23, 5 June 2010 (UTC)

Thanks, will do. (I clearly suck at this - I can't figure out how to reply...)
Hehe - you're doing fine. In a conversation like this, we usually use colons to make indents. It makes it easier to see when a conversation continues or finishes --annew 08:01, 6 June 2010 (UTC)
Oops - I forgot to tell you that you add your name and datestamp by hitting the signature icon just above the edit box - second from the right. --annew 08:02, 6 June 2010 (UTC)
I think I'm getting the hang of this. So, I finished the rekonq article and only minor edits remain. The next release (0.5.0) is due in a month or so, and I've marked things that need to be changed for that...
Meanwhile, I had a bunch of questions regarding how docs.kde.org/Handbook and the userbase wiki environment could work together. I tried to help out in the doc team a year or so back and the docbooks are insanely hard to get started with! At least, I found it slowed me down more than it helped and I didn't have that kind of time to invest back then. Would it not be better to use a wiki-style environment to edit the handbooks? And if so, wouldn't userbase be a perfect fit for that role? I should probably post this up for discussion on a mailing list, but I couldn't figure out whether to post it on kde-docbook or kde-doc-english. I suppose I'll go online on irc and ask.--karthikp@gatech.edu 09:36, 6 June 2010 (UTC)

Contents

Thread titleRepliesLast modified
The KRunner page515:22, 10 April 2012

The KRunner page

I'm sorry to say that your recent changes have completely broken the Translate system for this page - negating all work done so far by our translators. Since this material is almost all new we will re-tag it, but please be aware of the guidance for translation continuity - wherever possible keep the appropriate tag with its paragraph, even if you move the paragraph. Delete a tag attached to any paragraph deleted. Never add tags manually. Hope that helps Face-smile.png

08:49, 8 April 2012

Sorry, annew, I couldn't figure out how to handle the tags. The ominous warning said don't delete them, so I just grouped them all together and edited below them. Now I have a better idea of how to work with the tags!

In several pages, translate tags make up a considerable volume of the page. The warning at the head of the edit page is rather abstract. Your message is so much clearer. It would be good to replace the "don't delete the tags" warning with:

"[W]herever possible keep the appropriate tag with its paragraph, even if you move the paragraph. Delete a tag attached to any paragraph deleted. Never add tags manually."

I have one more suggestion; if at all possible, it would help to syntax highlight the translate tags with a barely visible gray instead of black. That will focus the attention on the text instead of the tags.

I have another related question. There were other ≪translate≫ tags (I can't put angle brackets here without this thing complaining about unbalanced tags) that I *had* to delete because otherwise, they were visible in the main document. What do those do?

09:05, 8 April 2012

Replacing the warning: OK, that makes sense. I'll try to get to it today - but if you become aware that it has slipped the net, don't hesitate to remind me.

I don't think it is possible for the translate tags to be greyed out, but I will point our web gurus to this thread and get their opinion.

Writing tags intended to be visible - it is done by adding nowiki tags - < nowiki>translate< /nowiki> will achieve this (NB I have added spaces into the nowiki tags to stop them being a command).

The multitude of translate tags - translators see only the text between translate tag pairs. Occasionally it is necessary to split things up in many places to make this work for the translators. One really big problem for them, though, is that if they only see part sentences they have no context, and in some languages that can cause incorrect translation. That's why we have the rule that a message should be completely within the tag pair. If you have a section where you can't work out where to put the pairs, either ask on #kde-www or ping me, Claus_chr or Yurchor for help.

11:16, 8 April 2012

I've re-written the warning - possibly over the top, this time Face-smile.png but try an edit and see what you think.

15:54, 9 April 2012

Much clearer! I have a few suggestions:

  • There's a bracket missing in first sentence. It should probably read, "Tags (such as <!--T:1-->)..."
  • Since the notice is really aimed at new editors, it could begin with a short introduction such as, "Userbase uses a tag system to mark paragraphs for translation. These tags (such as <!--T:1-->) are automatically added by the system."
  • I like the three simple bullets used to condense the info. Let's sort them in this order, though. I also reworded them to be even more clearer:
    • Do not add new tags.
    • If you move a paragraph, move its tag with it.
    • If you delete a paragraph, delete its tag with it.

Let's put it all together. What do you think of this new warning?


A note about translation tags: Userbase uses a tag system to mark paragraphs for translation. These tags (such as <!--T:1-->) are automatically added by the system.

  • Do not add new tags.
  • If you move a paragraph, move its tag with it.
  • If you delete a paragraph, delete its tag with it.

18:52, 9 April 2012

Compromise Face-smile.png I've used most of your wording, but kept my longer statement about not adding tags. Thanks for the input. Hopefully it is both more obviously seen and easier to understand now.

15:22, 10 April 2012
 
 
 
 
 

This page was last edited on 6 June 2010, at 09:36. Content is available under Creative Commons License SA 4.0 unless otherwise noted.