Template talk:Unit

Help please, if it's possible: assignment of Category should be something like {Type|Pagename} but w/o the leading 'unit:'.

Because, units should be listed alphabetically instead of showing up under 'U': Category:MechWarrior Online Units. ==Fleur, 6. Jan. 2012, 15:49 CET
 * It's necessary for unit pages to have a namespace of "Unit:". Otherwise, a unit named after a canon unit, like Clan Wolf or Kell Hounds, would create a page that would over write an actual page about that canon unit. Since they all need to have a namespace of unit, they will all show up under the letter U on a category page.--Seth 14:00, 7 January 2013 (CST)
 * dont want to change namespace of pages, just the sorting order within category. usually, with pagename-example 'xyz': First will sort 'xyz' under 'F'. no clue how to put that in this template. _Fleur_7.1.2013_22:00_CET
 * If you mean the default order of the sortable table, that listing is ordered by what faction they are aligned with. I could make the faction column move directly to the right of the unit name so that it's a bit more clear that is what they are being grouped by. --Seth 15:39, 7 January 2013 (CST)
 * Did it, that was what I meant, here Category:MechWarrior Online Units under 'Pages in category' all units are now listed under their name, instead of 'U'. Same with other categories Category:House Unit, etc (if u go back from redirect to category again)_Fleur_8.1.2013_13:18_CET

Languages
I like the idea of adding a primary language section to the online unit pages. What do you need help with?--Seth 14:11, 7 January 2013 (CST
 * ehm, nothing, think I did it, thx. - Forms (MechWarrior Online Unit): name='lorem ipsum' ... now, template unit: Create MechWarrior Online Unit: Unit: lorem ipsum
 * forminput is 'MWO Unit', leading to the ugly double, no idea how to stop that
 * is there a way to have the 'unit-name' from the form autofilled in the unit-template? will {pagename} work and user should manually delete 'unit:'?_Fleur_7.1.2013_23:06_CET
 * I think I understand. The problem with using {PAGENAME} is that it would lead to Unit:Unit: like you said. The unit namespace is automatically added to the entered unit name because all online unit pages must start with the Unit prefix. The person creating the online unit page will just need to enter the unit name twice. --Seth 17:26, 7 January 2013 (CST)
 * still not convinced; if {pagename} would be used, a hint may ask usr to delete the leading 'unit:' ... just to avoid typos, or what will happen, when the 2nd name entered doesnt match the previous one?
 * as things are now: Category:Speech =Fleur, 15.1.13, 17:43cet
 * The person using the form never has the opportunity to add or remove the unit: from the page name when using the form. That makes sure that the page name starts with unit:. It's been a while since I have edited that form, but I will see if I can simplify the unit name field so they only enter it once. Is that what you are trying to achieve?--Seth 14:00, 15 January 2013 (CST)
 * uhm, yes, exactly! first usr enters unit name, a page with 'unit:name' is under creation, what's the 2nd time asking for it good and will it make any difference with they dont match.gl, thx, bye=Fleur, 15.1.13, 21:49 cet

Looking good!
The unit pages have needed a facelift for a long while now.--Seth (talk) 22:21, 31 January 2013 (UTC)
 * Thx. note2self: sorting order within categories is dependent on, which may differ from 'unit:page-name'. Can easily be avoided, and set to right order with 'Basename', if unit's namespace is set up. I.e.: Unit:ComGuard is listed under 'G', for their 'name' is 'German ComGuards' >> think I already wondered why users are asked to enter unit's name twice; can users move pages? if not, it seems necessary to meet user's demands. If they can move pages (which is equally to rename the unit), we might put the confusing 'name' to an end and use page-name w/o namespace-prefix instead.
 * 'Command' still shows empty lines, but it's a brainsaw right now.==Fleur (talk) 00:00, 1 February 2013 (UTC)
 * I can't give you a solid estimate for that namespace extension. I think the problem with the command is that when on side of the table is taller than the other side, the content expands the it's inside while the other side remains only one line tall with a large black space above and below it. So far on the Mech Model and the Semantic equipment templates I have managed to keep the content of both sides the same height. A simple solution would be to increase the width of the entire info box or find some way to shrink the content of the cell.--Seth (talk) 05:03, 1 February 2013 (UTC)

Metadata displying twice
Checked in on the unit page to see how the new template displays, and the unit data is displaying twice (which on some systems pushes the free text down the page). ==Fiona Marshe (talk) 06:48, 1 February 2013 (UTC)
 * I havent removed the former info-box yet, so now both are being displayed. Will remove former box when I'm sure the new thing is working as expected.==Fleur (talk) 13:32, 1 February 2013 (UTC)

_NOTOC_
Why are we using _NOTOC_ on this?--Peckham33 talk Help is always given to those who ask for it 18:16, 6 February 2013 (UTC)