View source for Talk:Modify a Page

Jump to: navigation, search


Thread titleRepliesLast modified
Translation tags1118:03, 14 January 2012
Better #Workflow section416:33, 5 December 2011

Translation tags

We should expand upon the "don't add translate tags" warning and explain what the

languages /
tags are and how they should be handled.

(It seems like it didn't like the tags so I removed the <> for convenience.)

(This is mostly a note to myself, but if someone has time to do it before me - go ahead if you want.)

Hans17:50, 21 September 2010

For future reference, you need to use <nowiki></nowiki> tags around anything that mediawiki would see as a command.

annew07:19, 22 September 2010

Hm, I think I tried <pre></pre> and <nowiki></nowiki> but it still complained. Maybe I missed the latter, I'll find out when I write the text. :)

Hans11:16, 22 September 2010

What exactly are you going to write about? We have covered it in the appropriate pages. And pages are linked, wherever appropriate. Dulpication makes it hard to maintain.

annew12:40, 22 September 2010
Edited by another user.
Last edit: 08:14, 4 June 2011

Which pages would that be, Edit Markup? I think it's very relevant on this page, since you'll see it if you edit some pages, and many contributors are probably unsure of how to handle them. The first two tags only need a short mention, but <!--T:n--> should be explained in my opinion (what to do if you add, move or remove text etc.).

Hans14:35, 22 September 2010
Edited by 0 users.
Last edit: 17:39, 22 September 2010

The description of the task this page refers to says "Modify existing content, fix a spelling, clarify a description, add more details." Adding markup is not part of that task at all. The only markup that is relevant to this page is the warning to leave tags alone.

Please keep the tasks discrete.

annew17:39, 22 September 2010

It's not about adding markup, it's about how to handle the existing markup - i.e. the <!--T:n--> tags.

For most parts the contributor can just ignore them (modifying existing content), but what if he/she moves some text around or deletes some text? I also think we need to clarify what we mean by "NEVER add new translate section tags.", since some may not realize what <!--T:n--> are for and add them for the new text.

Hans17:46, 22 September 2010

The instructions for handling markup are on the page about preparing for translation, where they belong.

annew18:13, 22 September 2010

@annew, the problem is a simple cut and paste to a page section can result in <translate> tags appearing in preview and incomprehensible garbled internal errors like "Unbalanced </translate> tag."

Maybe leave the general instruction, but please can those errors link to something that gives you enough info to fix the problem? (I've spent 25 bloody minutes fighting --T5-- warnings and unmatched </translate> after a 2-line edit, and I've worked with SGML/HTML/XML for 26 years.)

(later...) I now realize that when editing a section, you're often presented with unmatched translate tags from this section title and the next section's title. Maybe they should always go inside the === === title markup?!
skierpage00:49, 13 January 2012

Better #Workflow section

The Modify a Page#Workflow section has some minor problems: don't say "hit", it's not a summary box, the button is "Show preview", rephrase "double-enter".

I fixed the section, it's in User:Skierpage/Improved_Modify_a_page. Can someone with write access please update this? Thanks.

skierpage00:09, 29 November 2011

I had forgotten that we protected some "instruction" pages. Mostly I agree with you. It is indeed a Summary field, not a box, however, that's a technical distinction, not really a general user one, so I haven't changed that. Similarly, you'll see that I've marked buttons as menuchoices - again they are not strictly so, but we have agreed with the translators and docbook producers that we should so mark anything that denotes a choice made by the user. If you see other buttons not marked so please feel free to add the markup. Let me know if you come across protected pages that need such attention. Thanks.

annew14:38, 29 November 2011

Actually, the protection was added because we were getting a lot of spam - some of it malicious. I think we have this under control now, so I'll try to set some time apart to find the protected pages and remove the protection.

annew14:39, 29 November 2011

Thanks for updating.

Yes, maybe field is too tech-y, I wonder if there's a better term. Summary text area , is no better? doesn't help ;-)

I noticed inconsistency between click on (the) X and click (the) X. I'd drop the "on", it's just noise.

skierpage23:44, 1 December 2011

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in one of the groups: Users, Administrators, trusted, KDEDevelopers.

You can view and copy the source of this page.

Return to Thread:Talk:Modify a Page/Better Workflow section/reply (4).


This page was last modified on 21 September 2010, at 17:50. Content is available under Creative Commons License SA 4.0 unless otherwise noted.