View source for User talk:Yurchor

Jump to: navigation, search


Thread titleRepliesLast modified
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
The ToolBox page507:32, 15 June 2011
WebWorld 2011103:30, 7 June 2011
Recent edit of KonsoleDevelpment309:28, 16 February 2011
Obsolete pages?219:37, 21 January 2011
Discussion input needed013:13, 13 December 2010
Localised Screenshots119:31, 23 October 2010
Загальні проблеми у KDE114:33, 11 October 2010
The Dolphin edit010:56, 6 October 2010
Plasma/FAQ919:33, 30 September 2010
Amarok pages111:14, 26 September 2010
"Chatty" pages - hard to mark up 311:31, 23 September 2010
Chihuahua012:56, 6 September 2010
First page
First page
Previous page
Previous page
Last page
Last page

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.

Claus chr (talk)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.

Yurchor (talk)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

Yurchor (talk)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)?

Yurchor (talk)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 then I can offer them to contact you. (talk)03:57, 12 July 2013

Answered at the email given.

Yurchor (talk)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

The ToolBox page

The translations of the ToolBox page are seriously out of date, and I don't think we can get them back in sync with the English page - it was at one time removed from the translation system and then reinstated much later, so now it thinks, that the existing translations are OK even though they are not.

Anne and I agreed that it is best simply to delete the existing translations. We'll wait a bit though, to give you time to rescue your work. Some of it can be reused.

From the page history it seems that your translation is quite recent, but still as far as I can see a translation of a fairly old version. Maybe the old translation units has been kept even after the English page was removed from translation?

Claus chr11:31, 12 June 2011

Ukrainian backup is done. ;)

Yurchor11:34, 12 June 2011

It seems that is possible to "repair" this. See User_talk:Caig#The_ToolBox_page_1211. I'll wait a bit longer, if you want to try it out.

Claus chr18:06, 14 June 2011

This is not the only affected page (I cannot find the others now, but I am sure). Well, I I will repair translation little by little then.

Yurchor19:02, 14 June 2011

In that case, I'd guess that PageLayout could be similarly affected. They were the first two Help files created.

annew07:15, 15 June 2011

Yes, it is. Thanks for the pointer.

Yurchor07:32, 15 June 2011

WebWorld 2011

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/WebWorld 2011.

Thanks for this complete report. Face-smile.png

Yurchor03:30, 7 June 2011

Recent edit of KonsoleDevelpment

I don't understand your comment. Surely, KonsoleDevelopment is the original page - or am I missing something?

Claus chr21:35, 15 February 2011

Consider the following situation:

1) User read the instruction and want to follow it. 2) He clicks the link and opens localized page (with Special:myLanguage). 3) He notice that the missing new "Bla-bla" section of Configuration.

Question: How to add the description of "Bla-bla" on localized page? Answer: The section should be added to the original page.

So what is the point to send the user to the localized page, right?

Yurchor21:48, 15 February 2011

I get your point. However, a user who knows enough to make additions to a page probably also knows how to navigate to the original page. On the other hand, a more casual user who perhaps doesn't even speak English might still be able to provide valuable suggestions on the Talk page.

I don't think that leaving out Special:myLanguage is going to be a problem to anyone - navigating to the translation of choice is easy enough; but I wonder if it is not a good idea to remain consistent even in special cases like this.

Claus chr09:21, 16 February 2011

Ok, I reverted my change.

Yurchor09:28, 16 February 2011

Obsolete pages?

I think the pages in this list pre-date the current translation system. Should they be deleted?

Вступ до KDE
Для чого призначено KDE
Ласкаво просимо до бази даних користувачів KDE
Освітні програми
Отримання довідки
Пошук програм
Програми/Мультимедійні програми
Робота з графікою і зображеннями
Таблиця еквівалентних програм
Як задавати питання
annew19:05, 21 January 2011

Yes, they are obsolete. Please delete them. Thanks for your work.

Yurchor19:16, 21 January 2011

Done :-)

annew19:37, 21 January 2011

Discussion input needed

Hi. Could you please read and comment on


annew13:13, 13 December 2010

Localised Screenshots

Zinchenko has the idea that by using .svg files from Inkscape it should be possible to make them language agnostic, so that translators could simply add applicable texts to the image. I have no idea whether this would work, or even whether it would be less work than creating a new screenshot. Would you mind talking to him about this? Thanks.

(By the way - have you noticed that it is now possible to translate the page title within the normal translation system?)

annew18:56, 23 October 2010

1) It works. At least for this file we have SVG-version which makes localization very easy. SVG can also be very helpful to keep uniform look and feel between the translated pages.

2) Yes, thanks.

Yurchor19:31, 23 October 2010

Загальні проблеми у KDE

This is the only remaining link to "General KDE Problems" - which is now just a re-direct. Am I safe in assuming that this is an obsolete page that can be deleted? All the information that was on that page and is still relevant has been moved onto other pages.

annew14:26, 11 October 2010


Yurchor14:33, 11 October 2010

The Dolphin edit

I have plastered warnings all over about not touching the tags, but still people edit without reading them :-( Thanks for rescuing things after this edit. I wish there was some way of making the tags untouchable, but I can't think of anything.

annew10:56, 6 October 2010


Plasma/FAQ is a redirect which always points to the latest version, so it's best not to use the link with the version number.

annew14:57, 29 September 2010

Sure. So, what to do if user is on 4.4 (4.3, 4.5 soon (hey, Plasma developers, where are you?), etc.) and wants to be instructed how to add a widget on his panel? ;)

Yurchor15:05, 29 September 2010

On every Plasma/FAQ/whatever page there is an info box directing to the earlier versions :-)

annew15:22, 29 September 2010

Not really... :-)

Yurchor15:29, 29 September 2010

Yes, really. 4.4 says For older versions you can turn to the KDE 4.3 specific page, theKDE 4.2 specific page, the KDE 4.1 specific page or the KDE 4.0 one

4.3 says For older versions you can turn to the KDE 4.2 specific page, KDE 4.1 specific page or the KDE 4.0 one

and so on. And they are all links.

annew17:19, 29 September 2010

The only page with these links is Plasma/FAQ. Aliasing of Plasma/FAQ with Plasma/FAQ/4.4 (4.3, 4.5, etc.) breaks all links on the translated versions (via Special:myLanguage). Subpages, like Plasma/FAQ/4.4/Configuration, have no aliases at all.

What is the solution for linking if we not use "/4.x/" in links? ;)

Yurchor17:30, 29 September 2010

I'm not sure that I'm understanding the problem but while looking at it, I did note that the Plasma/FAQ/4.4 (which is what the user is actually reading) didn't have Special:myLanguage at all, so I've fixed that.

Plasma/FAQ itself only contains the redirect to the latest version, and the redirect has to be changed when a new version is made. Apart from that, all the links have /4.x in them. I would have thought that between that and the myLanguage thing it would work. If it doesn't, can you explain a bit more about what actually happens? Thanks

annew17:53, 29 September 2010

Consider the following examples: 1. Plasma/FAQ#How does Plasma work? links to the English page.

Special:MyLanguage/Plasma/FAQ#How does Plasma work? in any locale you will also be linked to the English page (broken localized links).

2. Plasma/FAQ/4.4/Configuration is valid page that can be linked, e.g. Plasma/FAQ/4.4/Configuration#Can_I_move_the_applets_on_the_panel.3F

On the other hand

Plasma/FAQ/Configuration#Can_I_move_the_applets_on_the_panel.3F points to nowhere (broken subpages).

Yurchor18:06, 29 September 2010

Plasma/FAQ has only one purpose - to direct anyone searching to the latest version. It doesn't have any content, any sections, any subpages, so I'm surprised that even your first example works. I wouldn't have expected any links to be formulated against Plasma/FAQ at all - but against the versioned links (after all, the reader doesn't actually see that part of the link anyway). Now at last I understand where we started from :-) Yes, you are correct, I made a mistake there. Sorry about that, but I really did need to understand what you were pointing out.

annew18:27, 29 September 2010

Amarok pages

I did not do the original markup and I'd never looked at these pages. It looks as though they were done at the time that Siebrand thought we should tie down the translation to the nth degree. I've edited Amarok/QuickStartGuide, which should fix both your problem with images and my problem with section editing not working. Please let me know asap if it's now OK - if so I'll carry on with the others. If you want any other changes, I can do those at the same time.

annew10:59, 26 September 2010

Much better for me now, but... (oh, those curses from the other translators... Face-smile.png)

Yurchor11:14, 26 September 2010

"Chatty" pages - hard to mark up

Some pages have a chatty style that is difficult to mark up. Sometimes I am marking features as menuchoices, when they are not exactly so. I don't know whether this is the best approach, or not, so I'd appreciate advice. Examples of such are the KOffice pages, KWord, KSpread, KPresenter etc..

annew10:52, 22 September 2010

imho, these pages are by no means documentation, rather advertisement pages. Hence, there is no sense to use the same markup. Much more easily to use common wiki markup (quotes for emphasis, bold, etc.) for these pages.

Yurchor11:14, 22 September 2010

OK, I'll go through the KOffice pages and change those. If you meet similar inappropriate stuff, please change them and accept my apologies for the extra work.

Your description "rather advertisement pages" is, of course, exactly what they were in the first place, when UserBase was conceived as a showcase for apps, rather than as a place for documentation.

annew11:18, 22 September 2010

A discussion which started from the same place: Talk:Translation_Workflow#Use_of_menuchoice_tag_421. I'd like your input, please.

annew11:31, 23 September 2010

We are close to moving UserBase to the new Chihuahua theme. There are some big advantages with Chihuahua, not the least being the ability to adapt to screen space, both large screens and small, hand-held ones. Much of the work I've been doing lately has been to prepare pages for the switch. As always, with something new, there are likely to be issues that we are not aware of until it is in more general use, so I'm approaching all who have made significant contribution in the last seven days, asking for help.

I'd like you to change your User Preferences to use Chihuahua, as soon as possible. The plan at the moment is that if at the end of this week we have no show-stopper issues we will make Chihuahua the default theme for UserBase, probably next weekend.

There is a public Etherpad at - please add any notes, comments, issues there. It's also helpful if you say "Hi" in the chat window, because that ties a comment colour to your name, so I know who to approach if more discussion is needed.

Thanks for the help.

annew12:56, 6 September 2010
First page
First page
Previous page
Previous page
Last page
Last page

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