View source for User talk:Yurchor

Jump to: navigation, search


Thread titleRepliesLast modified
syntaxhighlight tag in manuals115:41, 31 March 2020
help: cannot save the FR translations 520:00, 5 August 2019
Problem on Kdenlive/Manual/Effects And Transitions307:59, 2 August 2019
not resizable square to put translated text314:23, 25 July 2019
Testing wikisandbox.kde.org211:07, 13 July 2019
Дякую…116:03, 7 June 2019
merging Typographical_guidelines & Toolbox into Userbase014:14, 20 May 2019
FAQ translation of TechBase deleted by Fuzzybot 208:33, 17 May 2019
System Settings118:22, 24 January 2019
Unused files222:01, 16 January 2019
Marking for Translation106:25, 26 December 2018
Manually added translation unit tags?106:34, 2 March 2018
DocBook conversion doesn't work009:51, 25 July 2017
One of our translators is enthusiastic, maybe a bit too enthusiastic.111:34, 15 January 2016
Konversation813:57, 28 November 2013
Your translations of my OpenPGP articles104:42, 12 July 2013
Long page names, and docbook needs217:23, 2 November 2011
New facility for Team Leaders017:25, 30 October 2011
Amarok Manual614:31, 24 September 2011
KMail/Security008:57, 17 July 2011
First page
First page
Previous page
Previous page
Last page
Last page

syntaxhighlight tag in manuals

Hi Yuri

I noticed that in the KDevelop5 manual some occurences of the Input template has been replaced by the syntaxhighlight tag (see fx Kdevelop5/Manual/Meet_KDevelop). Does this work well with the wiki2docbook program or should we advice the author against using it in a documentation contex?

15:32, 31 March 2020

Hi Claus,

It was discussed in kde-doc-english ML earlier. I will correct the script when converting this manual. Not a real problem for me.

Best regards,

15:41, 31 March 2020

help: cannot save the FR translations

Hi Yuri After your last validation of, I tried to translate in FR the new elements starting at '===Per Konsole tab Bash history ===' but I cannot save. I know I have met the same problem on Mediawiki () but generally submitting twice the EN modified page is sussisant. Here it doest not work. Cannot save nothing. See Maniphest T221119 : dummy update. Help

10:39, 4 August 2019

Yes. It is a known problem of the current version of the Translate extension. Please wait until the database will be updated (it seems we can do it only manually now). There is nothing I can do now. It is Carl's pet.

Meanwhile, you can translate something else. Sorry for this trouble.

10:44, 4 August 2019

Sorry for the trouble. :(

For now there is a script that will do this automatically, but will need to be restarted after each server restart and I created a sysadmin request to make it works after each restart.

12:13, 4 August 2019

No problems. Thanks for your help. Face-smile.png

12:16, 4 August 2019

The script should now always work. And restart itself after each server reboot. If the issue is still here, let me know and I will try to troubleshoot it with sysadmin.

20:00, 5 August 2019

ok works now. Thank you.

15:51, 4 August 2019

Problem on Kdenlive/Manual/Effects And Transitions

Hi Yuri

I am afraid I have made something of a mess out of your translation of Kdenlive/Manual/Effects And Transitions. All your translated text should be in place but the page displays nothing. I suggest we wait a couple of days to see if this is just fuzzybot playing up. I still have your original text so nothing is lost.

09:05, 1 August 2019

No need to worry. I will revise the translation by myself. Thanks anyway.

09:55, 1 August 2019

Everything is back to normal - your existing translations are back (I didn't touch your recent edits, of course). Silly mistake on my part - I simply forgot to close a brace matching comment.

07:57, 2 August 2019

Thanks. Yes, it works as expected now. Everything is in its right place. :)

07:59, 2 August 2019

not resizable square to put translated text

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in one of the groups: Users, Administrators, trusted, KDEDevelopers.

You can view and copy the source of this page.


Return to Thread:User talk:Yurchor/not resizable square to put translated text.

Added as an issue here. Thanks.

19:58, 24 July 2019

Should be fixed now.

12:37, 25 July 2019

much better ! similar back to previous behaviour and extendable to the right on the complete screen. Thank you.

14:23, 25 July 2019


Hello Yurchor,

I started a few days ago an update to the wikis and you can try it at More details are available at Could you take a look and provide feedback?



08:17, 7 July 2019

Just a note: translations are impossible after the update. Any change cannot be saved wit an error message:

This namespace is reserved for content page translations. The page you are trying to edit does not seem to correspond any page marked for translation.

Thanks in advance for fixing this issue.

09:40, 13 July 2019

Sorry for the trouble, this should now be fixed. Let me know if you still have problems.

11:07, 13 July 2019


…за всю вашу українську документацію. Приходжу я, випадкова людина, читати про Kdenlive, а тут уже (майже) все є. Дякую Smiley.png

Ipomoea (talk)16:01, 7 June 2019

Будь ласка. Хоча... Kdenlive у цьому перекладі — найслабше місце. Face-smile.png

16:03, 7 June 2019

merging Typographical_guidelines & Toolbox into Userbase

Hi Yuri, I ve open this subjet on Jucato's page. Do you have objections ?
14:14, 20 May 2019

FAQ translation of TechBase deleted by Fuzzybot

Hi Youri,

do you agree that each FAQ translation of TechBase was being deleted ?


Dear ChristianW,

The KDE TechBase page Translations:Development/FAQs/General FAQ/55/fr has been deleted on 16 May 2019 by FuzzyBot, see

.... and so on

Editor's su

12:18, 16 May 2019


Long story short: Yes.

Full-sized story:

KDE e. V. (or rather its Board of Directors) has decided to hire a professional documentation writer to improve our technical documentation. Now we should see what Jucato will do to reach his goal. That's all I can say.

13:39, 16 May 2019

System Settings

I read in phabricator, that there is a System Settings reorganization planed for Plasma 5.16, so I think that we should wait for 5.16 to be released, before we continue working on the system settings wiki pages (and relevant translation).

18:15, 24 January 2019

Ok. Our target is constantly moving. Documentation is a process. ;)

18:22, 24 January 2019

Unused files

Hi Yuri,

I just saw that this wiki has more than 1000 unused images: That should we do about this? Delete them, or just ignore them?

I wanted to use to track the remaining screenshots to update, but it's difficult to find old screenshots that are used somewhere.

15:46, 16 January 2019

I think it is safe to delete icons and screenshots for English locale. Localized screenshots with some low probability level can be reused. Do you need some help to do this?

16:48, 16 January 2019

Thanks I will start cleaning :D. If you want to help you are welcome. But I could also try to write a script to detect old screenshots that are still used, will probably be faster ;)

22:01, 16 January 2019

Marking for Translation


I noticed you marked some of the pages I edited for translation. I'm new to this, but I remember reading new content was automatically marked. Is there something I can do to help you out, perhaps making it myself after editing and adding content, so that you don't have to?

Aballach (talk)20:27, 25 December 2018

Yes, the breaking into translation units and providing them to the translators is automatic. But somebody has to trigger the process for every translatable page. Moreover, there are things that should be taken into account when doing so (fine granularity of the messages, bracket balance, using consistent numbering of the units). It also needs some additional wiki permissions.

Do you really want to mark the pages for translation? ;)

06:25, 26 December 2018

Manually added translation unit tags?

Hi Yuri

Firef has added to the pages Okular and KDE Wallet Manager. The content seems ok (I have only looked at it superficially); however, he seems to have added translation unit tags manually. Can you confirm this?

06:22, 2 March 2018

Sure. I have fixed this. Thanks.

06:34, 2 March 2018

DocBook conversion doesn't work

Hi Yuri

We have a problem with the DocBook conversion program - it doesn't work currently. I have filed a ticket with the sysadmins (and added you as subscriber to that ticket). Hopefully the problem can be solve on the server side.

09:51, 25 July 2017

One of our translators is enthusiastic, maybe a bit too enthusiastic.

Hey, I am one of the Krita manual writers.

We are moving our manual to, which is a mediawiki on kde servers. The benefit of this for us is that we have a bit more flexibility. We will of course be using the excellent translate extension.

Now, one of our translators is a bit confused about the relationship between Krita and KDE, being that Krita is part of KDE, and has put up the majority of our translation pages onto the 'ready for translation' todo, even though we told him not to.

I am not sure what is best now. We will not be updating the pages outside of 'our new docs are at' on top of each page. And I wouldn't want to give you too much work, but at the same time, I also don't want to confuse you in regards to huge amount of pages that appear and dissapear suddenly from the 'ready for translation' todo.

The topic where this is discussed is here: and I am online at #krita during european daylight.

What do you suggest?

Wolthera (talk)11:28, 15 January 2016

I have no problems with any of your solutions. And no confusions for sure. Everything's under strict control (RSS feed). ;)

Just ask if you want delete/move/do something else with your pages.

Many thanks for documenting Krita.

11:34, 15 January 2016


I started to translate the page , please check correctness.

Alex Talker (talk)19:50, 19 November 2013

Ok Face-smile.png

19:54, 19 November 2013


Alex Talker (talk)03:10, 20 November 2013

Here translate in .po file, idk, how to upload.

Alex Talker (talk)16:00, 20 November 2013

Imported. Can you try to import by yourself (Special pages -> Import translations)?

16:50, 20 November 2013

O, thanks, now me know.

Alex Talker (talk)17:07, 20 November 2013

Hello again.

Please, translate this page, it your general distribution, right?


Alex Talker (talk)13:40, 28 November 2013

Your translations of my OpenPGP articles


probably next Wednesday (July, 17th) an Ukrainian television crew ( will visit my OpenPGP course / Cryptoparty (in Berlin, Germany). For obvious reasons there is currently a hype here in Germany about crypto and privacy tools in general and about Cryptoparties in particular. Thus several German television crews will be there, too. Of course, I do not know what exactly they are going to send but if you have finished some of my texts until then then they may mention them (maybe link them from their web page). If you give me your email address (send it to [email protected]) then I can offer them to contact you. (talk)03:57, 12 July 2013

Answered at the email given.

04:42, 12 July 2013

Long page names, and docbook needs

I'm working through the pages available in the Kdenlive Manual, and trying to comply with the page and section markup that helps docbook. I've come across this problem where the Index page shows "Kdenlive on other Desktops and Operating Systems" and it is currently linked to Kdenlive/Manual/KdenliveOnOtherPlatforms. Clearly if a change is needed, now is the time to do it, but I'm not too happy about very long page names. What would be your recommendation in a case like this?

annew13:40, 2 November 2011

In this case there will be enough to add the anchor

<span id="Kdenlive on other Desktops and Operating Systems">

The general concern is that links should refer to Kdenlive/Manual/KdenliveOnOtherPlatforms#Kdenlive on other Desktops and Operating Systems

This method can be used to avoid renaming Amarok pages.

BTW can I just fix this (an everything else) at last and establish the sustainable process of further editing with the ability to generate DocBook any time? Face-smile.png

Yurchor13:51, 2 November 2011

I know Claus has been talking to you about various such concerns, and that he is building it into Draft:The KDE Documentation Primer. I'm picking up bits as I go along, and when your conversations are finished we should have the ability to generate DocBooks without too much effort - the aim is to have them at the point where they compile every time without needing extra work. Please carry on working with Claus on this, and meanwhile, make any changes you need. I'll learn the needs as quickly as I can Face-smile.png

annew17:23, 2 November 2011

New facility for Team Leaders

With today's update of the Translate extension, we have two new options in the "I want to" combibox -

Review all translated messages in... and Accept translations in.

These should be useful when you are checking on the work of new and relatively unknown translators. They are only available to translation Team Leaders, at least for now.

annew17:25, 30 October 2011

Amarok Manual

Regarding the latest edit of Amarok/Manual/AmarokWindow/PlaylistPane:

Could you please explain what the problem with the recent changes to the Amarok pags was. It is a problematic page, and we need to do something about the placing of images. Anne and I have been trying to make things look decent with little success. The latest attempt using a table is the only thing that has even come close to solving anything.

I agree, of course, that docbook conversion has top priority. Does that mean that we can't use tables for this kind of thing? Perhaps we simply need to force all images to be centered between sections? (That would make this page look very odd.) Any ideas would be much appreciated.

Claus chr09:59, 24 September 2011

Sorry for not explaining this earlier.

The script is trying to build bijection between two markups. To be clear, the problems with your last edits are as follows

  1. Script assumes that each raw of the table begins with "| ". Adding <translation> tag gives the XML output "|
    Message" That moves Message outside the table in the converted docbook
  2. KDE docbook commands subset does not have command to scale columns (although generic docbook does). This breaks the current parser (it thinks that "| width="75%" |" is the cell content).
  3. <br /><br /> is not parsed at all (<para></para><para></para> just triggers the warning).

Surely these problems can be fixed by improving the script. Any help will be appreciated. Instructions can be found here.

P.S. Docbook syntax does not allow using images in captions to images. Please avoid using images templates in the captions. Thanks.

Yurchor11:03, 24 September 2011

Thanks, this is helpful.

How does KDE docbook handle tables? Is it possible to give some hint of what the column width should be? Could we make, say, 4 colums and then merge 3 of the (an ugly kludge, off course, but if it works...). Or should we avoid tables all together?

Claus chr11:15, 24 September 2011

Q: Is it possible to give some hint of what the column width should be? A: No, it will be chosen automatically to fit the width. Images will not be scaled down (will be shown as is (100%)).

Q: Could we make, say, 4 colums and then merge 3 of the (an ugly kludge, off course, but if it works...)? A: You could, but the script in its current form does not parse this. Just for the reference the code in docbook for

Jumping around in code
Ctrl+Alt+O Quick open file: enter part of a filename and select among all the files in the current session's projects' directory trees that match the string; the file will then be opened


  <tgroup cols="2">
    <colspec colname="c1"/>
    <colspec colname="c2"/>
    <entry namest="c1" nameend="c2">Jumping around in code</entry>
    <entry>Quick open file: enter part of a filename and select among all the files in the current session's projects' directory trees that match the string; the file will then be opened</entry>

The problem is in smart parsing for the number of columns to be merged. I have to do it manually for KDevelop manual conversion.

Q: Or should we avoid tables all together? A: No. Generic tables are parsed well. Screenshot

Yurchor11:41, 24 September 2011
Edited by author.
Last edit: 14:05, 24 September 2011


The table width doesn't seem to be as big an issue as I thought. At least when the uploaded images have a sensible size, tables seem to adjust to them nicely.

I tried one more time to make a table to solve the problem, but in a test page User:Claus_chr/Test. Would this work? (apart from the <br /> problem - I havent found out what to do about that yet.)

Update: As a matter of fact I don't need the br tags at all - I just misread the wikimedia docs.

PS. Anne and I was wondering about your comment about images in captions. As far as we know there never was an image in any caption. What are we missing here?

Claus chr11:55, 24 September 2011

Q: Would this work? A: No. See 1. Can you keep the pipe ("| ") in one unit with the rest of the cell? If you do, then modified script can give something like this.

P.S. I should concentrate on my report now. Can we discuss the rest later? Thanks for your answer.

Yurchor12:57, 24 September 2011


I wasn't aware of that page at all until yesterday, when I was checking for subpages not translatable. I imagine that it was originally copied from TechBase, and probably by me. Pity I didn't realise that there was no value whatsoever, as I spent a lot of time preparing it :-) Anyway, it is now moved to the Archive namespace and removed from the Translate system. Thanks for the heads-up.

annew08:57, 17 July 2011
First page
First page
Previous page
Previous page
Last page
Last page

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