[latex3-commits] [git/LaTeX3-latex3-latex3] master: Re-order l3backend-color (d79977357)

[Joseph Wright]

Repository : https://github.com/latex3/latex3
On branch  : master
Link       : https://github.com/latex3/latex3/commit/d7997735766188645bcfd1a0b3ebf3f210e20102

>---------------------------------------------------------------

commit d7997735766188645bcfd1a0b3ebf3f210e20102
Author: Joseph Wright <joseph.wright at morningstar2.co.uk>
Date:   Mon Dec 7 22:56:02 2020 +0000

    Re-order l3backend-color
    
    This is preparation work for exploiting new (x)dvipdfmx
    features when available.


>---------------------------------------------------------------

d7997735766188645bcfd1a0b3ebf3f210e20102
 l3backend/l3backend-color.dtx | 86 +++++++++++++++++++++----------------------
 1 file changed, 43 insertions(+), 43 deletions(-)

diff --git a/l3backend/l3backend-color.dtx b/l3backend/l3backend-color.dtx
index 49a148c35..fded86452 100644
--- a/l3backend/l3backend-color.dtx
+++ b/l3backend/l3backend-color.dtx
@@ -67,49 +67,6 @@
 % \texttt{dvipdfmx}/\XeTeX{} is PDF-based means it (largely) sticks closer to
 % direct PDF output.
 %
-% \subsection{\texttt{dvipmdfx}/\XeTeX{}}
-%
-%    \begin{macrocode}
-%<*dvipdfmx|xetex>
-%    \end{macrocode}
-%
-% These backends have the most possible approaches: it recognises both
-% \texttt{dvips}-based color specials and it's own format, plus one can
-% include PDF statements directly. The latter are not subject to the stack,
-% so are not suitable for general use. Of the two stack methods, the dedicated
-% one has been extended to cover color spaces, so it is used in preference to
-% the \texttt{dvips} one.
-%
-% The \LaTeXe{} backend code uses \texttt{dvips}-based code with
-% \texttt{dvipmdfx}/\XeTeX{}, and so we leave getting color from \LaTeXe{} to
-% a shared code path below.
-%
-% \begin{macro}
-%   {
-%     \@@_backend_select_cmyk:n  ,
-%     \@@_backend_select_gray:n  ,
-%     \@@_backend_select_rgb:n
-%   }
-% \begin{macro}{\@@_backend_reset:}
-%    Push the data to the stack.
-%    \begin{macrocode}
-\cs_new_protected:Npn \@@_backend_select_cmyk:n #1
-  {
-    \__kernel_backend_literal:n { pdf: bc ~ [#1] }
-    \group_insert_after:N \@@_backend_reset:
-  }
-\cs_new_eq:NN \@@_backend_select_gray:n \@@_backend_select_cmyk:n
-\cs_new_eq:NN \@@_backend_select_rgb:n \@@_backend_select_cmyk:n
-\cs_new_protected:Npn \@@_backend_reset:
-  { \__kernel_backend_literal:n { pdf: ec } }
-%    \end{macrocode}
-% \end{macro}
-% \end{macro}
-%
-%    \begin{macrocode}
-%</dvipdfmx|xetex>
-%    \end{macrocode}
-%
 % \subsection{\texttt{dvips}-style}
 %
 %    \begin{macrocode}
@@ -297,6 +254,49 @@
 %</luatex|pdftex>
 %    \end{macrocode}
 %
+% \subsection{\texttt{dvipmdfx}/\XeTeX{}}
+%
+%    \begin{macrocode}
+%<*dvipdfmx|xetex>
+%    \end{macrocode}
+%
+% These backends have the most possible approaches: it recognises both
+% \texttt{dvips}-based color specials and it's own format, plus one can
+% include PDF statements directly. The latter are not subject to the stack,
+% so are not suitable for general use. Of the two stack methods, the dedicated
+% one has been extended to cover color spaces, so it is used in preference to
+% the \texttt{dvips} one.
+%
+% The \LaTeXe{} backend code uses \texttt{dvips}-based code with
+% \texttt{dvipmdfx}/\XeTeX{}, and so we leave getting color from \LaTeXe{} to
+% a shared code path below.
+%
+% \begin{macro}
+%   {
+%     \@@_backend_select_cmyk:n  ,
+%     \@@_backend_select_gray:n  ,
+%     \@@_backend_select_rgb:n
+%   }
+% \begin{macro}{\@@_backend_reset:}
+%    Push the data to the stack.
+%    \begin{macrocode}
+\cs_new_protected:Npn \@@_backend_select_cmyk:n #1
+  {
+    \__kernel_backend_literal:n { pdf: bc ~ [#1] }
+    \group_insert_after:N \@@_backend_reset:
+  }
+\cs_new_eq:NN \@@_backend_select_gray:n \@@_backend_select_cmyk:n
+\cs_new_eq:NN \@@_backend_select_rgb:n \@@_backend_select_cmyk:n
+\cs_new_protected:Npn \@@_backend_reset:
+  { \__kernel_backend_literal:n { pdf: ec } }
+%    \end{macrocode}
+% \end{macro}
+% \end{macro}
+%
+%    \begin{macrocode}
+%</dvipdfmx|xetex>
+%    \end{macrocode}
+%
 % \subsection{Separations}
 %
 % Here, life gets interesting and we need essentially one approach per