Difference between revisions of "User talk:AN_TRN_26"

From War Thunder Wiki
Jump to: navigation, search
(Undo revision 169099 by U152205114 (talk))
 
(66 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
{{DISPLAYTITLE:User talk:AN_TRN_26}}
 
{{DISPLAYTITLE:User talk:AN_TRN_26}}
 
+
{{Userbox |id = [[File:Msg-info.png|60px|none]] |id-background = white |info = Discord ID: '''AN_TRN_26#9210''' |info-font-size = 10 |border = black }}
 +
{{DISPLAYTITLE:User talk:AN_TRN_26}}
 +
{{Userbox |id = [[File:Msg-info.png|60px|none]] |id-background = white |info = [[User talk:U64962917/Archive/2019]] |info-font-size = 10 |border = black }}
 +
{{Break}}
 +
__TOC__
 
== Visual Editing - Some mistakes to avoid ==
 
== Visual Editing - Some mistakes to avoid ==
  
Line 8: Line 12:
 
[[File:VisualEditing-Instruction_Block.png|210px|thumb|right|Instruction block as viewed through the '''Visual Editor''', note the exclamation mark in the circle.]]
 
[[File:VisualEditing-Instruction_Block.png|210px|thumb|right|Instruction block as viewed through the '''Visual Editor''', note the exclamation mark in the circle.]]
  
 
+
;How to convert text to hidden on the final version
 
+
*Using the visual editor, I notice wiki paragraph instructions tend to get deleted, which they should not.  These serve as reminders especially for future new editors which may make updates, edits or changes and will need those instructions as to what needs to go where.  If the information has been added, we don't want the instructions to show, however, we don't want them deleted either.  To render the instructions invisible we use the comment brackets '''<nowiki><!--</nowiki>''' and '''<nowiki>--></nowiki>''', anything between those will show up on the editing page, but not on the final page, allowing the instructions to remain intact, but not show on the final product.  Utilizing the visual editor, what you do is highlight the instruction set, right-click and select "cut".  Next, in the toolbar, click on the "Insert" drop-down and select "! Comment". A popup box should show up where you "cut" the instructions from and here go ahead and right-click in the box and select "Paste" which should paste the instructions within the box. Click the "Insert" button and you should now have a new comment with the instructions which will be available for future users, but not show up on the final page.
 
 
 
 
 
 
 
 
 
 
  
  
Line 24: Line 23:
 
* Do not remove parser and template functions, these will show up as a puzzle piece with a name afterwards (such as "Specs", "Break", "Battle-rating" or such).
 
* Do not remove parser and template functions, these will show up as a puzzle piece with a name afterwards (such as "Specs", "Break", "Battle-rating" or such).
 
[[File:VisualEditing-Template_Parser.png|210px|thumb|right|For parsers and templates, not the existing puzzle piece and name following.  These will now show the actual output during usage of the Visual Editor.]]
 
[[File:VisualEditing-Template_Parser.png|210px|thumb|right|For parsers and templates, not the existing puzzle piece and name following.  These will now show the actual output during usage of the Visual Editor.]]
 
+
<br>
 
+
<br>
 
+
<br>
 
+
<br>
 
+
<br>
 
+
<br>
 
+
<br>
 
+
<br>
 
+
<br>
 
+
<br>
 
+
<br>
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
== Editing Questions Here ==
 
== Editing Questions Here ==
Hello, AN_TRN_26.  Thanks for reaching out to me.  I wanted to know where I can find information on the "Details" ("Features", "Limits" "Optimal Velocities", and "Compressor") of planes.  So far, I can't find the info for any of these via the in-game UI.  Could you point me to where they are?
+
(post your questions here)
Sincerely,
 
~KN_940 23:09, 25 February 2019
 
 
 
 
 
Hello. I've got a question about categories. Earlier each faction and category had at least brief explanation "what are those" in general, or what's their specialty on top of their page. Were those removed on purpose, or it's just an accident? Also, is it okay to translate mechanics guides from .ru wiki to transfer to here? If so, should I shortcut the screenshots and so on from there directly, or re-upload those here? Also, if I was to make ground-based radar page, is there any tooltip, that can show, that page is unfinished or something? (since there I can only provide info for 1 type of those, and there is 2 or 3 as far as I know.) --[[User:U42773747|U42773747]] ([[User talk:U42773747|talk]]) 07:44, 11 April 2019 (UTC)
 
  
:Hello bangerland, 1) With the change to the new wiki, there really isn't the same place to have brief explanations of the different categories and so they were not migrated. If you feel there is a place to have it, let me know and we can consider it. 2) It is fine to go ahead and translate any mechanic pages from the Russian Wiki which we don't have yet. If you understand Russian that will make it easier, if not Google Translate will get you in the ballpark and you can tweak it from there (https://wiki.warthunder.com/I-29 is a page I did that with just to do it, it was a fun exercise). Go ahead and upload the screenshots to our wiki, if possible, replace any screenshots with Russian (or in Russian) with ones in English.  If you cannot get an English equivalent, make sure in the caption you briefly explain what is stated in Russian. 3)As far as a page for the ground-based radar, if it is in the game (like the airborne radars) we should be able to add them. Use the airborne radar page (https://wiki.warthunder.com/Airborne_Radars) as an example to go by.  If it is not in the game and you are wanting to write up a historical page about them, we should be able to find/create a category for them so people will know not to expect to find it in the game, but can read up on it for historical facts (sneaky way to educate people!). As you are working on the pages, if you want us to evaluate what you have as you go, just leave a note in the summary line for any of the moderators to take a look and make suggestions. Good luck! [[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 10:43, 11 April 2019 (UTC)
+
* Hi, regarding formatting on your userpage: instead of using a bunch of linebreaks to manually keep sidebars within sections, you could use <code><nowiki>{{clear}}</nowiki></code> ([[Template:Clear]]), which will automatically "wait" for the sidebar to end before continuing with subsequent text or sections. - [[User:U38088265|U38088265]] ([[User talk:U38088265|talk]]) 15:47, 17 August 2022 (UTC)
  
:: Categories: Well, I'm not thinking that every category needs brief tellings, but faction explanations were nice (at least on base level, like, which types of shells they generally use and what does it mean.), though on different ranks situation changed drastically, so idk. On other hand, something like helicopters page may need short explanation. As in, many players do not understand why support helis even exist in the game. I clearly can tell now, that support helicopters can dodge radar SPAA fire by doing maneuvers, dropping altitude, etc., so they have a purpose now. Plus I feel like the stat cards of helis don't really explain their strong and weak sides, and they're generally all same per faction. As in: USA - powerful main turret, but can carry only 4/2 pilons with weapons. USSR - slow, and main turret is lacking, but attack helicopters can carry 4 pilons of "main" payload and 2 pilons of "sub" payload, resulting in ability to carpet bomb enemy SPAA with rockets while doing your job, and support helicopters can add bombs (they work, lol). German - More 3d mobility, than the rest support helicopters. French - Faster turn rate (Q\E), I think?... I mean, I may be wrong about those, but it still took me weeks to understand it all. \\ Page transerfs: Well, I can read Russian, so it wont be an issue. I guess i'll try when I have time. \\ radar page: I guess I just make one then and then put comments in place of things I do not have, right?  --[[User:U42773747|U42773747]] ([[User talk:U42773747|talk]]) 13:47, 11 April 2019 (UTC)
+
::Hello DnaGonite, thanks for the information, I will give it a try!! Always something to learn, thanks!! (Update - it is much cleaner looking!!  Thanks for the tip!!) --[[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 03:46, 18 August 2022 (UTC)

Latest revision as of 05:23, 16 August 2023

Msg-info.png
Discord ID: AN_TRN_26#9210
Msg-info.png
User talk:AN_TRN_26/Archive/2019


Visual Editing - Some mistakes to avoid

Visual editing brings an alternative way to edit a wiki which does not require you to wade through wiki code. A few things to remember:

  • Do not remove instructions from the different sections of a page (typically identified by an exclamation mark in a circle), a simple mouseover will expand on the entire instruction set.
Instruction block as viewed through the Visual Editor, note the exclamation mark in the circle.
How to convert text to hidden on the final version
  • Using the visual editor, I notice wiki paragraph instructions tend to get deleted, which they should not. These serve as reminders especially for future new editors which may make updates, edits or changes and will need those instructions as to what needs to go where. If the information has been added, we don't want the instructions to show, however, we don't want them deleted either. To render the instructions invisible we use the comment brackets <!-- and -->, anything between those will show up on the editing page, but not on the final page, allowing the instructions to remain intact, but not show on the final product. Utilizing the visual editor, what you do is highlight the instruction set, right-click and select "cut". Next, in the toolbar, click on the "Insert" drop-down and select "! Comment". A popup box should show up where you "cut" the instructions from and here go ahead and right-click in the box and select "Paste" which should paste the instructions within the box. Click the "Insert" button and you should now have a new comment with the instructions which will be available for future users, but not show up on the final page.




  • Do not remove parser and template functions, these will show up as a puzzle piece with a name afterwards (such as "Specs", "Break", "Battle-rating" or such).
For parsers and templates, not the existing puzzle piece and name following. These will now show the actual output during usage of the Visual Editor.












Editing Questions Here

(post your questions here)

  • Hi, regarding formatting on your userpage: instead of using a bunch of linebreaks to manually keep sidebars within sections, you could use {{clear}} (Template:Clear), which will automatically "wait" for the sidebar to end before continuing with subsequent text or sections. - DnaGonite (talk) 15:47, 17 August 2022 (UTC)
Hello DnaGonite, thanks for the information, I will give it a try!! Always something to learn, thanks!! (Update - it is much cleaner looking!! Thanks for the tip!!) --AN_TRN_26 (talk) 03:46, 18 August 2022 (UTC)