Difference between revisions of "User talk:AN_TRN_26"

From War Thunder Wiki
Jump to: navigation, search
(Editing Questions Here)
(Undo revision 169099 by U152205114 (talk))
 
(39 intermediate revisions by 6 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:
+
;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 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.
+
*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 33: Line 37:
 
(post your questions here)
 
(post your questions here)
  
* Regarding border line in Italy section: Well, you see, the white line next to rank 6 "otomatic", which separates normal and premium vehicles, is absent. This is what i've tried to do there. Not sure what your revert did there. (the browser is IE9, which displays no line there.) PS: it is gone again. --[[User:U42773747|U42773747]] ([[User talk:U42773747|talk]]) 11:48, 17 May 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)
::It appears to be a browser issue as with using Chrome, all vertical and horizontal lines are white (and there, none missing), however with Firefox, all vertical lines are there and are white, while all horizontal lines are black.  I don't have IE so I can't test that.  I wonder if there were browsers updates which broke the viewing mechanic? [[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 11:58, 17 May 2019 (UTC)
 
::: hell if i know. IE9 didn't update for ages already, as you know it was stopped renewing after Win7 release or so. I don't have any visual discrepancy in any other section, so i just figured i could fix the hole in a fence, you know. ''SIGH''. Here is what it looks like on my screen, just to confirm that i'm not insane or doing it for kek's: --[[User:U42773747|U42773747]] ([[User talk:U42773747|talk]]) 12:07, 17 May 2019 (UTC)
 
[[File:A visual bug in italian section.png|thumb]]
 
::::I believe you, for a while, I primarily used Firefox but ran into similar problems, Chrome seems to be the most stable of the browsers I have used. I will forward this up and see if any of the other Mods or Devs have run into this and if so, is there a fix. [[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 12:11, 17 May 2019 (UTC)
 
:::::I usually use firefox at home, its just that I don't really stare onto pages this meticulously when I have something else to do, so I usually don't notice this. BY THE WAY, now that I look at it, the 7-th rank number is in reverse compared to the rest, and it's like this in most if not all sections. Should the number be in front of "rank" or after? --[[User:U42773747|U42773747]] ([[User talk:U42773747|talk]]) 12:15, 17 May 2019 (UTC)
 
::::::Yes, the 7th rank number is backwards, should be the same as other ranks with "#" then "Rank". [[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 12:24, 17 May 2019 (UTC)
 
:::::::Ok, pushed them in proper place where noticed. Also, while I looked through those pages I found out that Germany plane page has same border issue for me, as in there is no separation line in rank 5 section. --[[User:U42773747|U42773747]] ([[User talk:U42773747|talk]]) 12:32, 17 May 2019 (UTC)
 
:::::::: Welp, that's one way to solve a problem, lol. The border is now in place as it should be, with absence of rank 7. Didn't even notice that Ariete was rank 6. Also, if I'd apply the | symbol to german plane section of rank 5, the border would return and it looks normal. Does it cause any collision in other browsers, just so I know later on? --[[User:U42773747|U42773747]] ([[User talk:U42773747|talk]]) 13:59, 17 May 2019 (UTC)
 
:::::::::I am not seeing any problems with the German aircraft rank 5 section.  Looks fine in both Firefox and Chrome. [[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 14:09, 17 May 2019 (UTC)
 
 
 
* Hello. How does one rename page without damaging all the links that lead to it? Do we use "move" function with redirect or something like that? --[[User:U42773747|U42773747]] ([[User talk:U42773747|talk]]) 12:32, 5 June 2019 (UTC)
 
 
 
== Question Archive ==
 
(go into edit mode to view)
 
<br>
 
<!--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?
 
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)
 
 
 
:: 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)
 
 
 
::: I see where you are coming from with the explanations, just not sure at this time where they would fit.  I believe that is part of the direction we are trying to go with the individual vehicle page, description section and usages in battle could reflect much of what you are talking about, but more specifically for each helicopter (aircraft, tank, ship...etc...) because while some variations aren't much different, others are. A TL;DR paragraph could be added with all of the necessary goodies to get started without having to read the entire article and then someone can come back and read the whole thing when they are ready.  Right now many articles are lacking, but that is why we are all here for, we can write them and then they can be updated as people gain experience with them and use them. I've been hopping around working on articles (https://wiki.warthunder.com/AN-M30A1_(100_lb) and https://wiki.warthunder.com/M.B.157), but there are still a lot to do.  Go ahead with the radar page, we can look at it and go from there. [[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 14:12, 11 April 2019 (UTC)
 
 
 
Another question - how does one add vehicles into "faction class tank" categories? Can't pinpoint USA medium tank page, to add Merkava MK1 to "Israeli" tab. It also seem to have weird space, perhaps a bugged link? Also, all new vehicles from event so far have broken spec-cards and icons. IDK what to do with that. --[[User:U42773747|U42773747]] ([[User talk:U42773747|talk]]) 08:45, 24 April 2019 (UTC)
 
 
 
: In regards to the icons for the new vehicles, those will need to be created on the Russian wiki side and then copied to our wiki (uniformity), they have not made the icons yet so that is why the image is broken on the button. The new pages for the event vehicles will be created either by Volgaigor or Inceptor57, once they are in, we can start working on them.  To edit vehicles on the USA medium tank page (or expandable menu), you will need to edit the template.  In the search bar, type in "Template:USA medium tanks" and as you type it you should see it auto fill, select it and then just edit the template directly (adding the new vehicle). It is pretty straight forward in the template layout. [[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 10:03, 24 April 2019 (UTC)
 
 
 
:: So, basically, until they added spec-cards I can't do anything about either of these things. Template feeds from spec-card link as well, as I see. By the way, Magach 3 link from card specs has blank spaces in front of it, which caused the visual bug I mentioned. Uh well, later then. --[[User:U42773747|U42773747]] ([[User talk:U42773747|talk]]) 10:51, 24 April 2019 (UTC)
 
 
 
==About Centering Text in a Table==
 
 
 
Hi! Is this the place to ask any editing-related questions? If so, I'm trying to figure out how to center stuff in tables and make it full-width. I tried source-editing, but I can't figure it out. I went to google, but it gives the same answer: style="text-align:center" and width:"100%", but it doesn't seem to work. If anybody can redirect me somewhere, or just explain this, I would appreciate that. --[[User:U36258839|U36258839]]
 
 
 
: Hello Criminal, yes you can ask editing questions here.  The answer you posted should work, depending on how you format it in the table, here is an example:
 
* |style="text-align:right;"| 52
 
 
 
* There are a couple of tables on the page https://wiki.warthunder.com/G.A.M.Mn_50_(50_kg) which left, right and center justify, you can look at the coding to see how its set up.  If you run into issues, create the table in your name page and I can look at it (others might too) and offer suggestions on how to get you where you want the table to be.  --[[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 19:54, 3 May 2019 (UTC)
 
 
 
:: Ah, that's such a face-palm for me. To make it work I needed to add the semi-colon inside of the quote marks, like so: style="text-align:right;". That reference article definitely helped, thanks! On a side-note, how do you have that signature after your answer? I can only hand-write it, is that it?: --[[User:U36258839|U36258839]] ([[User talk:U36258839|talk]]) 21:03, 3 May 2019 (UTC)
 
 
 
::: Not a /facepalm but a learning moment, learning has occurred and that is good!! See your page for more information. [[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 20:10, 3 May 2019 (UTC)
 
 
 
== About "So-ki" Type 2 20mm gun ==
 
 
 
Hi,
 
 
 
You wrote to me:
 
 
 
"Secondly, in the historical section for the So-Ki you mentioned the Type 98 20 mm cannons and also mentioned the Type 2 20 mm cannons. At this time, War Thunder has the vehicle listed as using the Type 98 cannons and that is what we need to reference in the writing. I looked at the Wikipedia page and several other linked references (including Sensha's page - unfortunately, he did not cite his work to look at further) and the references I looked at all seemed to circle back on themselves with no real credible primary or secondary sources cited. I do not doubt that Type 2 20 mm cannons were the final choice as they were newer (1942 as opposed to the Type 98 - 1938), lighter and had faster muzzle velocity. My recommendation is to try to find at least one primary source (a technical manual, repair manual or other such original documents) or two or more secondary sources such as a book covering the history of Japanese military vehicles or other published book/document which cites sources the information was pulled from. If you can find either the primary or secondary sources which document the So-Ki actually would have gone into production with the Type 2 20 mm cannons, then you can submit a bug report War Thunder Forum (follow the instructions there) and the information may be forwarded to the developers for consideration to change the gun type listed in the game. If you should have any questions, please let me know. - AN_TRN_26 (talk) 00:17, 1 May 2019 (UTC)"
 
 
 
I found a primary source!
 
 
 
I posted a question on here: https://www.forum.axishistory.com/viewtopic.php?t=241905
 
 
 
As Akira Takizawa states "The main gun of that tank is not Type 98, but Type 2 20mm AA gun. There is no manual about that tank, because it was only experimental. Note that So-Ki is the designation of AA gun, not of tank. Type 2 20mm Twin AA gun was called So-Ki. So-Ki mounted on tank was called So-Ki II. So-Ki is stated in the development plan 1943 of IJA 1st Technical Laboratory as below."
 
 
 
Theregore can I post a bug report on War Thunder Forum to change the Type 98 mm gun to Type 2 20mm gun?
 
 
 
Additionnally the tank was called "So-Ki II" and not "So-Ki"
 
 
 
Regards,
 
 
 
Alexandre
 
 
 
: Hello. I’m not AN_TRN_26, but I can offer my perspective. Bug reports are not handled by the wiki so we don’t have first-hand influence on it. However, please make sure you have enough information as per bug report guidelines to make the report, as detailed [https://forum.warthunder.com/index.php?/topic/406397-ground-forces-armour-3d-and-damage-model-issues-important-read-before-posting/&ct=1556828442 here on the forums]. I wish you the best of luck! --[[User:U28580205|U28580205]] ([[User talk:U28580205|talk]]) 20:22, 2 May 2019 (UTC)
 
  
:: FYI, I am working with Theoask79 to find enough primary/secondary resources surrounding the So-Ki (or So-Ki II as the new document notes) and if they pan out have him submit a bug report. I am working on getting an OCR setup to try and translate the documents available to see if I can get a decent translation before going forward as I don't read Japanese beyond a few characters (and definitely don't want to have a bug report submitted with erroneous information - trust, but verify!). [[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 22:12, 2 May 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)