Hi Karl,
Am 06.08.2013 um 10:02 schrieb SCHUH Karl, SCHUH-TV:
Hi Erik, I understand, that the list on the todo-page is not finished yet, but I still don't know, if someone should start translating the DNS-forwarding immediately or not? If the list contains only sampla-data, it should be noted so (in "warning"-box).
The data in the list are no sample-data, so indeed a translation should be done immediately.
If the list contains first, but true, data, it should be synchronized to the workflow-satus (you say it is in C or D, but the list and the document still say B). As I said earlier, it would be nice to see who was the author and who revied the document (could be one or two lines in the head or foot of a document).
Good idea, so it is possible to see who reads through or made some corrections in which state of the workflow. A good location for this is the foot of the document i think. Another category can be if the explained functions was tested or not.
I agree with you, that ideas should be collected from anyone and that it would be nice to know who did what. But I don't think, that a spreadsheet is a good soluton since it is too easy to change something by mistake.
Do you think the chance for mistakes are relevant ?
I also ask you to think about a sort of "owner" for the primary-language-page and for each translation. These owners could be contacted, if someone wanted to do some changes.
If you click into the sidemenu of each wiki page you can find the option "old revisions" in there you can overlook all the changes and the authors who did the changes. This function can be used for this for example.
Maybe we should also have a glossary of words, we do not translate (server, port, client .......)
I don´t understand the intend for this, may you can explain it a little more.
Greetings, Karl
Greetings
Erik
Hi Karl, this list was a first idea of how the working progress can be listed. So the list isn´t finished until now, it might be important to find a good harmony also in relation to the workflow. The next step should be to figure a good way out for a spreadsheet, where all are invited to advect new ideas. For example if someone did some work on the wiki he can comment it in there what was done or what should be done in a closer future. Also a list of wikis which should be revised can be a good idea. But there is surely more.
The DNS forwarding wiki is meanwhile in phase (C) or may (D), but it is important to know what work was done until now, how many people did a review on that page and so on. As you see the workflow and a potential ToDo list is in the beginning and possibly a discussion with more ideas to this theme will come.
Greetings
Erik
Am 05.08.2013 um 19:18 schrieb SCHUH Karl, SCHUH-TV:
Hi Erik, thank you for your mail about the documentation-workflow, but I still don't get it :-(
The table says about "DNS forwarding", that translation should be done. On the other hand it (and the document itself) say, that this doc is in stage B, which means "authoring"? :-/
How shall I interpret this?
Best regards, Karl
-- Ing. Karl SCHUH
Hauptstraße 23a A-7434 Bernstein +43(664)38 06 107 _______________________________________________ Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
-- Ing. Karl SCHUH
Hauptstraße 23a A-7434 Bernstein +43(664)38 06 107
Hi Erik,
The data in the list are no sample-data, so indeed a translation should be done immediately.
I will start shortly.
If the list contains first, but true, data, it should be synchronized to the workflow-satus (you say it is in C or D, but the list and the document still say B). As I said earlier, it would be nice to see who was the author and who revied the document (could be one or two lines in the head or foot of a document).
Good idea, so it is possible to see who reads through or made some corrections in which state of the workflow. A good location for this is the foot of the document i think. Another category can be if the explained functions was tested or not. Do you think, someone will write a docu without doing, what he describes???
Do you think the chance for mistakes are relevant ? Maybe not, if it is just for collecting ideas.
If you click into the sidemenu of each wiki page you can find the option "old revisions" in there you can overlook all the changes and the authors who did the changes. This function can be used for this for example. Sorry, I forgot about that :-(
Maybe we should also have a glossary of words, we do not translate (server, port, client .......)
I don´t understand the intend for this, may you can explain it a little more. You will know the example of the "Speicherstapelzeiger" vulgo stackpointer. There are some terms that are usually used by all people working in IT, but their german translation is not. So how would you translate server? Diener? Dienstanbieter? ..... port? Türe? Tor? and so on. On one hand, the translators had a list of words, they don't have to translate or even should not translate. On the other hand, people who do not the meaning of these words could look them up there.
Greetings, Karl
I will start shortly.
O.K. great, if you are finished let it me know i will go for a review then.
If the list contains first, but true, data, it should be synchronized to the workflow-satus (you say it is in C or D, but the list and the document still say B). As I said earlier, it would be nice to see who was the author and who revied the document (could be one or two lines in the head or foot of a document).
Good idea, so it is possible to see who reads through or made some corrections in which state of the workflow. A good location for this is the foot of the document i think. Another category can be if the explained functions was tested or not.
Do you think, someone will write a docu without doing, what he describes???
No :-), but difficult to know if someone have checked a docu (may there was nothing to change) and there was no feedback or a note, so how can be figured out in which state of the workflow the actual documentation is then?
You will know the example of the "Speicherstapelzeiger" vulgo stackpointer. There are some terms that are usually used by all people working in IT, but their german translation is not. So how would you translate server? Diener? Dienstanbieter? ..... port? Türe? Tor? and so on. On one hand, the translators had a list of words, they don't have to translate or even should not translate. On the other hand, people who do not the meaning of these words could look them up there.
I think there is the need to know something about the IT matter if you write or translate some documentation, so words like port or server, etc. should be familar, otherwise we have the problem that the whole context can be lost. Another problem is that there are tons of words in the IT, firewall or router theme where no german translation exists, so a potential list is a big challenge i think.
Greetings
Erik
Am 06.08.2013 um 10:42 schrieb SCHUH Karl, SCHUH-TV:
Hi Erik,
The data in the list are no sample-data, so indeed a translation should be done immediately.
I will start shortly.If the list contains first, but true, data, it should be synchronized to the workflow-satus (you say it is in C or D, but the list and the document still say B). As I said earlier, it would be nice to see who was the author and who revied the document (could be one or two lines in the head or foot of a document).
Good idea, so it is possible to see who reads through or made some corrections in which state of the workflow. A good location for this is the foot of the document i think. Another category can be if the explained functions was tested or not.
Do you think, someone will write a docu without doing, what he describes???Do you think the chance for mistakes are relevant ?
Maybe not, if it is just for collecting ideas.If you click into the sidemenu of each wiki page you can find the option "old revisions" in there you can overlook all the changes and the authors who did the changes. This function can be used for this for example.
Sorry, I forgot about that :-(Maybe we should also have a glossary of words, we do not translate (server, port, client .......) I don´t understand the intend for this, may you can explain it a little more.
You will know the example of the "Speicherstapelzeiger" vulgo stackpointer. There are some terms that are usually used by all people working in IT, but their german translation is not. So how would you translate server? Diener? Dienstanbieter? ..... port? Türe? Tor? and so on. On one hand, the translators had a list of words, they don't have to translate or even should not translate. On the other hand, people who do not the meaning of these words could look them up there.
Greetings, Karl -- Ing. Karl SCHUH
Hauptstraße 23a A-7434 Bernstein +43(664)38 06 107 _______________________________________________ Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
documentation@lists.ipfire.org
-
Erik K. -
SCHUH Karl, SCHUH-TV