Difference between revisions of "Talk:Wiki Technical Guide"

From EncyclopAtys

Jump to: navigation, search
(Easy to discriminate?)
m (Easy to discriminate? {{OK}})
 
(7 intermediate revisions by 4 users not shown)
Line 3: Line 3:
 
:I did so in FR. I think I had not yet time to export in other languages. So, thx to had done it here :) -- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 18:29, 30 June 2019 (CEST)
 
:I did so in FR. I think I had not yet time to export in other languages. So, thx to had done it here :) -- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 18:29, 30 June 2019 (CEST)
  
== Easy to discriminate? ==
+
== Easy to discriminate? {{OK}}==
  
 
{{quotation||This facilitates discriminated responses in their consideration, implementation, etc.}}
 
{{quotation||This facilitates discriminated responses in their consideration, implementation, etc.}}
Line 15: Line 15:
 
::;Second one: Amosys has seen that long text couldn't be well displayed in game with the IG web tool. So he suggested to split long page in some other. For me it's not a problem at all and I can give you thousand of solution already used bay contributors: one of my preferred is: [[Primes_Raider]].
 
::;Second one: Amosys has seen that long text couldn't be well displayed in game with the IG web tool. So he suggested to split long page in some other. For me it's not a problem at all and I can give you thousand of solution already used bay contributors: one of my preferred is: [[Primes_Raider]].
 
::We have so many solutions in the wiki :) -- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 18:57, 30 June 2019 (CEST)
 
::We have so many solutions in the wiki :) -- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 18:57, 30 June 2019 (CEST)
 +
:::Ooops... sorry for the involuntary illustration of the very (first) point your "Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc." was raising.
 +
:::;First point: I realize that, in my answer to Heernis, I just forgot the context (which is not of '''all''' pages but only of '''talk''' pages). So, I think '''your''' answer will be more understandable by Heernis than mine. Grytt :-).
 +
:::;Second point: This one came to my mind precisely because of my misunderstanding of the context, and, though I totally agree with you as for solutions of the WebIG issue, it have not to be raised here. Sorry again :-(
 +
:::::No prob, Maupas, you just gave the demonstration of cutting a problem in little slice to solve it easier :) Demonstration is always better then speech ;) I suppose we can close with a '''{{OK}}''' -- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 20:32, 30 June 2019 (CEST)
 +
:::--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 20:03, 30 June 2019 (CEST)
 +
:::: I guess you both didn't understand. But I've found the error in my head. "discriminate" have 2 meanings: "differentiate" and "be prejudiced". As German was thinking of "diskriminieren" in the manner of  "prejudge" because there is no word for "distinguish" called like that it have always a negative meaning. So  I was thinking: "It facilitates to be prejudged". Good to know, but I should describe my topics better. It was a question about translation i do offline in German. Nothing more.
 +
::::--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 22:44
 +
 +
=== Some other reasons to slit an article into several shorts one: ===
 +
# '''categories'''. You can much more have very precise categories. For ex, [[Chat/RC FAQ]] is for all users, but [[Chat/Translation in RC]] (previously in RC FAQ) is for teams only => Translation in RC can have teams categories related. (and you can get the content of an article within an other one => the reader won't see any difference, when using '''noinclude''' wiki tags).
 +
# important text, '''easier to maintain'''. For ex, for a new features, you would want to add it on several pages, and need to update several pages if it changed (for ex: DeepL translations in IG channel).  Better create an short article, import it inside the pages: when it will change, you just update the short one, and all pages will be updated (using '''noinclude''' wiki tags).
 +
::::: --CraftJenn, Ranger du Cercle du Bois d'Almati ([https://chat.ryzom.com/direct/Craftjenn sur RC]) 11:39, 12 April 2020 (CEST)
  
 
== Preventing discussion by indicating the link? ==
 
== Preventing discussion by indicating the link? ==
Line 21: Line 33:
 
:I replaced the "weird" sentence ('''prevent''' is NOT the right verb, no :-)) as follows:
 
:I replaced the "weird" sentence ('''prevent''' is NOT the right verb, no :-)) as follows:
 
:“''So, please notify the ones you think concerned about the talk by adding the link to it in their own user talk page.''” Feel free to improve it, tough!--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:33, 30 June 2019 (CEST)
 
:“''So, please notify the ones you think concerned about the talk by adding the link to it in their own user talk page.''” Feel free to improve it, tough!--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:33, 30 June 2019 (CEST)
 +
::And it's so true, that I answered here as soon as I could!!! ;)
 +
::Have a look in my [[fr:Discussion_utilisateur:Zorroargh#Wiki_Technical_Guide_.E2.9C.93|discussion page]], Heernis, to see hwo Mapas did  -- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 19:07, 30 June 2019 (CEST)

Latest revision as of 10:39, 12 April 2020

New(?) templates

I created Template:OK () and Template:KO (), but I am wondering if those don't already exist with an other name. If they do, please let me know. Maupas (talk) 00:33, 9 June 2019 (CEST)

I did so in FR. I think I had not yet time to export in other languages. So, thx to had done it here :) -- Zo'ro-Argh Woren Siloy 18:29, 30 June 2019 (CEST)

Easy to discriminate?

This facilitates discriminated responses in their consideration, implementation, etc.

Really? It sounds like: "This (Writing 50 titles instead of 1 title for 50 topics) make it easy to discriminate responses in consideration, implementation, etc."
Better: "This prevent discriminated responses in their consideration, implementation, etc." Or what should there be said?
--Heernis (talks) 30. June 2019 - 14:22

Of the french text written by Zorroagh I understood that the one who want to modify, (or ask/answer questions about, or translate) some topic will find and work on this topic more easily if it is a short one. Hence my "faithful" translation of "Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc."
But I agree that this point of view is questionable (after all, sections are not so difficult to reach and work on) and I suspect the main reason for such a recommendation (systematical splitting of articles) is the difficulties encountered in implementation of wikis in WebIG.
More, your question raise the point of translation. In fact, as I'am not a native EN speaker, the present EN Wiki Technical Guide need to be checked by somebody who is AND understands FR enough (you know that's how we work in Translation Team). I don't know if we have among ourselves wikis contributors such a person but I think we could at least add a status reading "Proofreading requested" in the TIP template. What do you think?--Maupas (talk) 17:16, 30 June 2019 (CEST)
Not sure I understand.
Reading you, I have the impression that we mix up two subjecs.
First one
In my mind I wrote "Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc." in some context as forum or chat in where it's more a long marathon of interrupted and intertwine interventions not very easy to use as a problem statement. So I probably, because I have no time to find where I said this, I suggested to write a single problem to solve, for instance here. In my mind it would not be so hard to do titles end subtitles in discussion pages? I'm very puzzled and ask myself if I understand you.
Second one
Amosys has seen that long text couldn't be well displayed in game with the IG web tool. So he suggested to split long page in some other. For me it's not a problem at all and I can give you thousand of solution already used bay contributors: one of my preferred is: Primes_Raider.
We have so many solutions in the wiki :) -- Zo'ro-Argh Woren Siloy 18:57, 30 June 2019 (CEST)
Ooops... sorry for the involuntary illustration of the very (first) point your "Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc." was raising.
First point
I realize that, in my answer to Heernis, I just forgot the context (which is not of all pages but only of talk pages). So, I think your answer will be more understandable by Heernis than mine. Grytt :-).
Second point
This one came to my mind precisely because of my misunderstanding of the context, and, though I totally agree with you as for solutions of the WebIG issue, it have not to be raised here. Sorry again :-(
No prob, Maupas, you just gave the demonstration of cutting a problem in little slice to solve it easier :) Demonstration is always better then speech ;) I suppose we can close with a -- Zo'ro-Argh Woren Siloy 20:32, 30 June 2019 (CEST)
--Maupas (talk) 20:03, 30 June 2019 (CEST)
I guess you both didn't understand. But I've found the error in my head. "discriminate" have 2 meanings: "differentiate" and "be prejudiced". As German was thinking of "diskriminieren" in the manner of "prejudge" because there is no word for "distinguish" called like that it have always a negative meaning. So I was thinking: "It facilitates to be prejudged". Good to know, but I should describe my topics better. It was a question about translation i do offline in German. Nothing more.
--Heernis (talks) 30. June 2019 - 22:44

Some other reasons to slit an article into several shorts one:

  1. categories. You can much more have very precise categories. For ex, Chat/RC FAQ is for all users, but Chat/Translation in RC (previously in RC FAQ) is for teams only => Translation in RC can have teams categories related. (and you can get the content of an article within an other one => the reader won't see any difference, when using noinclude wiki tags).
  2. important text, easier to maintain. For ex, for a new features, you would want to add it on several pages, and need to update several pages if it changed (for ex: DeepL translations in IG channel). Better create an short article, import it inside the pages: when it will change, you just update the short one, and all pages will be updated (using noinclude wiki tags).
--CraftJenn, Ranger du Cercle du Bois d'Almati (sur RC) 11:39, 12 April 2020 (CEST)

Preventing discussion by indicating the link?

Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion.

This sound weird. Should be rewritten. (Think more simple ;-) )
--Heernis (talks) 30. June 2019 - 14:35
I replaced the "weird" sentence (prevent is NOT the right verb, no :-)) as follows:
So, please notify the ones you think concerned about the talk by adding the link to it in their own user talk page.” Feel free to improve it, tough!--Maupas (talk) 17:33, 30 June 2019 (CEST)
And it's so true, that I answered here as soon as I could!!! ;)
Have a look in my discussion page, Heernis, to see hwo Mapas did -- Zo'ro-Argh Woren Siloy 19:07, 30 June 2019 (CEST)