|Thread title||Replies||Last modified|
|The new KDevelop manual||6||19:39, 14 October 2017|
|The new KDevelop manual||12||19:40, 19 September 2017|
|test||0||14:41, 20 August 2017|
I have started a new thread for this ongoing conversation - the indentation was beginning to be a bit disruptive :-)
I see from your last entry that I have misunderstood what you were doing: I thought you were taking the old KDevelop4 handbook on UserBase as your starting point, but now I gather that you are actually working from a docbook version. This may pose a problem: The translations I copied over were for the KDevelop4 pages on UserBase and may not match up with the texts you got from the docbook.
Technical problems aside we should think about the implications of this: It is not a good idea to have two versions of the manual being developed in parallel - that will almost certainly lead to inconsistencies. Have you taken over responsibility for the KDevelop5 manual? In that case you may decide to develop the manual on UserBase and request, that other contributors do the same. Otherwise it might be better to continue working on the docbook (even though I agree with you that docbook xml is not nice to work with).
There is currently no simple way to convert docbooc to wiki format (the other way is somewhat easier - I have plans to automate both conversions but it is a non-trivial task and not my first priority). Once you decide that UserBase is the way to go I can help you with transferring the pages. But first I think we should check the pages already transferred for inconsistencies between the docbook text and the translated text on UserBase, so that we can mark the translation units that are not up to date.
"I see from your last entry that I have misunderstood what you were doing: I thought you were taking the old KDevelop4 handbook on UserBase as your starting point, but now I gather that you are actually working from a docbook version. This may pose a problem: The translations I copied over were for the KDevelop4 pages on UserBase and may not match up with the texts you got from the docbook. "
-This is not true. In the start we will copy all the manual 4 and move it to manual 5. Some programmers in the chat told me that the docbook that exists at the Git has new updates. My task is to bring those updates to the manual 5 on UserBase, as a second step. Third step is to change only the UserBase to the latest kdevelop5 features not the docbook because we will have only one copy which will be the UserBase.
But first I think we should check the pages already transferred for inconsistencies between the docbook text and the translated text on UserBase, so that we can mark the translation units that are not up to date.
-Yes, we will do that.
Thats I relief :-). In that case we have no problem with the pages already created. Do I understand you correctly, that I can go ahead and transfer the remaining pages from the KDevelop4 wiki pages? If so, I can probably get it done over the weekend.
I guess you were asking if there is an easy way to get pure text out of a docbook? I'm afraid this is not the case.
yes, go ahead and move the remaining pages :) :).
and Yes this is what I was asking. You see my bad english brought this mess. But I believe everything are ok now.
I noticed that the first two pages of the new KDevelop5 manual was almost identical to the equivalent KDevelop4 pages. I assume, that many more KDevelop4 pages can be copied into the new manual and just modified a bit. For the first two pages I copied all the translated units to the new pages, but this is a somewhat tedious task, so I wonder if it would be possible to do this smarter.
It should be possible to clone a page including all translations by a single command (we have never tried it, so I would have to do a bit of experimentation to be sure). The idea is that you would clone a page with all the existing translations, modify whatever needs to be changed; and then when the new page is marked for translation, only the modified sections would be flagged for translation.
Does that sound acceptable to you? If so I could try to clone the next page you are going to work on.
You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page.
Don't worry about the finer details of editing. Just start writing. It is easy enough to correct formatting mistakes; I usually patrol all new pages that I am aware of. You will get the hang of it as you go along.
As to translation I am happy to answer any questions you may have (and eventually include the material in a new introduction to translators).
We are aware that the guidance for writers and translators is not very good. Improving it is on our to do list. I should very much appreciate your feedback as work on the new introduction progresses. I have made a page for the Introduction to new contributors - nothing there yet, though. If you would like to follow the progress of that page, you can set a watch on the page and be notified whenever something changes there. And of course you are very welcome to contribute :-)
My question to you is about the new pages you have made about KDevelop5. I noticed that you took the contents of the equivalent KDevelop4 page and copied it with few modifications. That indeed seem to be a good way to get started. If you intend to proceed that way, I think we can actually employ a feature of the wiki software to transition existing translations along with the content. I wanted to know if it would be ok with you to do so; if so I can find out how to proceed and explain the process. The advantage of this way of doing it is that translators would only have to worry about stuff that is actually changed in the new manual.
Hi and sorry for the late answer. Yes I am interested and I would like you to show me how to do the procedure. Please give some guides about that feature of the wiki.
Great. I'll experiment a bit and let you know the results soon.
As to guides to the wiki - there is some (actually quite a lot) of material, which you can find on the Tasks and Tools page and the pages it links to. Unfortunately the material is somewhat disorganised; we are working on improving it so any feedback is welcome.