Difference between revisions of "User talk:AN_TRN_26"
(Edits.) |
(Edits.) |
||
| Line 19: | Line 19: | ||
* 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 == | ||
| + | (post your questions here) | ||
| + | * | ||
| + | * | ||
| + | * | ||
| − | + | == 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? | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | == | ||
| − | 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, | Sincerely, | ||
~KN_940 23:09, 25 February 2019 | ~KN_940 23:09, 25 February 2019 | ||
| Line 96: | Line 97: | ||
:: 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) | :: 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) | ||
| + | --> | ||
Revision as of 17:34, 6 May 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.
- 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 <!-- 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).
Editing Questions Here
(post your questions here)
Question Archive
(go into edit mode to view)
