https://bugzilla.wikimedia.org/show_bug.cgi?id=41716

David Chan <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #36 from David Chan <[email protected]> ---
I think we should be *extremely* restrictive about where language rules can
leak. This is because they lead to several problems:

(1) Rule changes make it hard to give a faithful real-time view of *any*
plaintext.

(2) Rule changes can cause unexpected errors in distant text.

(3) Few people can proofread both zh-Hans and zh-Hant. Therefore, almost anyone
who makes an edit will be unable to proofread at least one of the variants it
might affect.

On the other hand, leaking currently allows pages to import rules. I think we
should preserve this facility but make it more separate. 

1. In general, there should be no leakage: rules should be page-global, and
should not leak into or out of templates.  This means template *arguments*
should be subject to the rules of the page in which they are written, but text
generated by a template should not.  

2. As an exception to the "no leakage" rule, there should be a new type of
template called a Glossary, whose only purpose is to leak rules into the
calling page. That way, language rules are completely separate and independent
of any other template behaviour. These Glossaries should be referenced at the
top of the page only.  

3. The page which defines a template is free to use rules and Glossaries too.
But they will only affect the text generated by the template itself -- they
won't leak into any text defined in the calling page. This includes the
arguments passed into the template, because they're written in the calling
page.  

As you can see, this is just cscott's "Global" proposal, but with the
additional restriction that the templates that leak rules cannot have any other
functionality.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to