This is the
talk page for discussing improvements to the
WikiProject Wiki Syntax page. |
|
Archives: 1 |
I just went over some of the triple quote items, and a lot of them are missing quotes in the {{
succession box}} template. What seems to happen is that the fields are bolded by the template itself. However, sometimes someone wants to give further information about the person in the field that should not be bolded. So people have been added closing triple quotes, which are being found as errors because the opening quotes come from the template. (Of course, there really is an error: the original closing quotes in the template become opening quotes without closing quotes.) I've been fixing these by adding ''' 
to the end of the field. (See
[1] for an exmaple of this.) The   is because otherwise transclusion yields a string of six quotes which the wiki parser does not interpret as wanted, and the fields seem to have extreme whitespace characters truncated, so we have to use this.
Anyway, I'd like to encourage everyone to use this solution. If anybody thinks of another way to handle this that might be better, please mention it here. Eric119 05:39, 6 December 2005 (UTC)
This is the
talk page for discussing improvements to the
WikiProject Wiki Syntax page. |
|
Archives: 1 |
I just went over some of the triple quote items, and a lot of them are missing quotes in the {{
succession box}} template. What seems to happen is that the fields are bolded by the template itself. However, sometimes someone wants to give further information about the person in the field that should not be bolded. So people have been added closing triple quotes, which are being found as errors because the opening quotes come from the template. (Of course, there really is an error: the original closing quotes in the template become opening quotes without closing quotes.) I've been fixing these by adding ''' 
to the end of the field. (See
[1] for an exmaple of this.) The   is because otherwise transclusion yields a string of six quotes which the wiki parser does not interpret as wanted, and the fields seem to have extreme whitespace characters truncated, so we have to use this.
Anyway, I'd like to encourage everyone to use this solution. If anybody thinks of another way to handle this that might be better, please mention it here. Eric119 05:39, 6 December 2005 (UTC)