New lite text markup language based on pair quotes (pq)

 ┌───┬───┐ │ 4 │ 5 │ ├───┼───┘ │ 1 │ ├───┴───┐ │ 0 │ └───────┘ 

It looks like the opening square bracket [ .
Very easy to remember.

Initially, I planned an alternative option for specifying tags. Here is this:
[[H]Header/[-H]]
or
[[H]Header/[-]]
or
[[H]Header/]

Accordingly, the tables were set by the tag [[T]...]
The column delimiter was this - []
The line delimiter was [[]] - [[]]

Example table:

  [[T]
 A [] B [] C
 [[]]
 1 [] 2 [] 3
 [-T]] 

or so:

  [[T]
 [[]] A [] B [] C
 [[]] 1 [] 2 [] 3
 [-T]] 

(The [-] closing tag can be omitted.)

But then I remembered that several choices for the same formatting are something that I don’t like in Markdown (for example: ____ or **** ), and I decided to leave two formatting options in the PC markup ( ~'...' and [[~]...] ) will be wrong. So, it makes sense to leave only one form of the record - with quotation marks '' , since it is less conflicting and is the first / main idea that initiated this text markup {and the fact that typing quotation marks ' and ' unusual - I think not so scary, because [ from my point of view ] it is more important to read the markup and its cognitive characteristics (easy to understand / remember the rules of markup, easy to read / perceive the marked text), as well as reducing the likelihood of conflicts (when simple text or formula [ wrong / ] unamer It is interpreted as markup) and avoiding the need to screen something (otherwise you can often skip / not notice such errors - when the marked text was converted a little to what was intended)}.

Having made my choice in favor of quotes, at first I wanted to make such a line delimiter - '' (by analogy with [] ), but quickly changed my mind (because then there is a problem with empty cells in the table itself) and came to the current form of writing:
'
''A' 'B' 'C''
''1' '2' '3''
'
or so:
''
'A' 'B' 'C'
''
'1' '2' '3'
''

_{(Of course, this form of recording is not the most pleasant for typing and I thought a lot about whether it is possible to simplify it somehow (or at least give the possibility of an alternative, simpler form for writing tables, like in GitHub Flavored Markdown or in Habrahabr Flavored Markdown [ By the way, most implementations of Markdown do not support tables without headers ] ), but decided to stop at the current form of the record, since it is so light enough (compared to HTML <table>) and at the same time has an undeniable advantage [ over a simpler form record] - the ability to include yache ku table anything (including any other elements of the mark, and even nested tables), as well as the current form of writing makes it possible to use the spaces at the beginning and end of a line of any table (possibility controversial, but it can be useful to export database tables) of the cell.)}

The reasons (by the way, quite subjective), why I chose the characters '' (and not `´ or, say," "or “” ):

1. They look nice enough (in the appropriate font [ for example, Courier New ] ). In my opinion, better than "" or ‹.
2. They follow one after another in any encoding (as opposed to `´ or“ ”or‹ ›) [ as well as “” ] .
3. Why not “” - in Russian texts the double symbol “ is „ ( Screen typography. Quotes ).
4. And I also like the codes [/ years] of these characters ...

   201? and 201¿

One significant minus of the quotation marks ' and ' is that the single quotation mark character ' according to the current Unicode standard is the preferred character as an apostrophe character, and in many documents and web pages in English, the ' character is actually used as an apostrophe (for example : Don't ), including - in the generated documentation for Python , however in HTML-code it uses the HTML entity recently used there recently ’ , and in the source rst-files of the documentation the usual apostrophe is used - so both html (when using ’ ) and rst-files can be enclosed in ' such ' quotes without problems [ and, by the way, the most well-known [ me ] typographers (with rare exceptions) insert HTML entity ’ [ or ’ or ' or ’ ] , and not directly the closing quote character itself, and if you look at the largest English-language news resources, you can see that many of them simply use the apostrophe character (contrary to the recommendations of the Unicode Consortium) as an apostrophe) , but if there is such a need , the PC markup allows you to insert an unmatched opening ' and closing ' quotation mark: so `'` or so ''' (see Advanced Formatting Features. Raw \ Raw HTML ).

Another minus [ quotes characters ' and ' ] is the ambiguity of displaying the characters ' and ' in many popular fonts. In particular, in Consolas, used in GitHub and Bitbucket. In general, the characters of pair quotes in different fonts look different (including in monospaced programming fonts):

[ In my opinion, this simply shows that, in general, there is no clear / unambiguous idea of ​​how these characters should look. ]

(By the way, on Habré the characters of single double quotes were displayed quite acceptable (at least in Windows) due to the use of Verdana for the main text and Courier New for the code, but a few months ago the font for the main text of the articles was changed to Arial, because of I had to tweak the article a little - replace 'and' with ' and ' (in pq: `'` and `'` ).)