@@ -112,7 +112,7 @@ considered below. In all cases, it is necessary to encode, in a way or
112112another, that the config file uses the new syntax, so that Matplotlib can tell
113113which file-parser to use.
114114
115- Maintain a matplotlibrc-likelayout
115+ Maintain a matplotlibrc-likesyntax
116116```````````````````````````````````
117117
118118The config files would maintain the format
@@ -195,6 +195,16 @@ document how to do it using ``urllib`` if we really want to) of style sheets,
195195which I believe is a good enough replacement (but I am happy to hear arguments
196196that it is not).
197197
198+ (Lack of) changes for the end-user
199+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
200+
201+ For the end user, calls to ``matplotlib.style.use `` are unchanged. If
202+ maintaining the *same * naming convention, then the lookup mechanism stays the
203+ same and there is no ambiguity as to what file should be loaded. If the naming
204+ convention is changed (e.g. ``.mplstyle-v2 `` with the matplotlibrc-like syntax,
205+ or ``.py ``\( !) with the full Python syntax), then a simple priority policy
206+ (such as "always prefer the newer syntax if available") can be implemented.
207+
198208Implementation
199209--------------
200210