[BUG] Org-LaTeX-export: >> and << (inside of ~code~/=verbatim=) gets exported to single monospace symbol instead of 2 monospace symbols [9.5.5 (release_9.5.5 @ /usr/share/emacs/28.2/lisp/org/)]

["Garid Z." <garidzorigoo@gmail.com>]

I tried to export following org file (table) to PDF via
org-latex-export-to-pdf. 

* Test Org-file
|---+----------+----------|
| 1 | =>=      | =<=      |
| 2 | =>>=     | =<<=     |
| 3 | =>>>=    | =<<<=    |
| 4 | =>>>>=   | =<<<<=   |
| 5 | =>>>>>=  | =<<<<<=  |
| 6 | =>>>>>>= | =<<<<<<= |
|---+----------+----------|
| 1 | ~>~      | ~<~      |
| 2 | ~>>~     | ~<<~     |
| 3 | ~>>>~    | ~<<<~    |
| 4 | ~>>>>~   | ~<<<<~   |
| 5 | ~>>>>>~  | ~<<<<<~  |
| 6 | ~>>>>>>~ | ~<<<<<<~ |
|---+----------+----------|

Resulted PDF file has » and « symbols (maybe: U+00BB, U+00AB)
instead of 2 normal < symbols.


From the org manual:
> Text in the code and verbatim string is not processed for Org specific
> syntax; it is exported verbatim.


So, I believe it should've exported 2 normal < symbols (verbatim), not a
single (U+00BB, U+00AB) symbol.

------------------------------------------------------------------------

I think, it's a very similar case with double (or more) ==
characters in the code/verbatim. I recently reported this similar case:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=5ac1ebaa1

Solution for this might be almost identical with the previous fix.
Maybe something like:

+    (cond ((equal m ">>") ">{}>{}")
+    (cond ((equal m "<<") "<{}<{}")


Best,

Garid Zorigoo
------------------------------------------------------------------------


Emacs  : GNU Emacs 28.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.36, cairo version 1.17.6)
 of 2023-01-03
Package: Org mode version 9.5.5 (release_9.5.5 @ /usr/share/emacs/28.2/lisp/org/)
-- 
Garid Z.