Convert tblkch latex to web whitepaper v2

[fakela]

Converted the TBL whitepaper from the original LaTeX source (https://github.com/ton-blockchain/ton/blob/master/doc/tblkch.tex) to Markdown.
This version replaces the earlier PDF-based conversion.

Closes the following:

#114
#547

Known differences (to be fixed in future releases):

• Blackboard bold (\mathbb{}) fixes ([#1066](Double check and fix rendering of mathbb font in web whitepaper #1066))
• Italic formatting consistency — deciding when to use \mathit{} vs Markdown italics ([#1068](Use of \mathit{} vs Markdown italics #1068))
• Render issues for formulas on small screens in the web whitepaper (scroll visibility and overflow) ([#1069](Render issues for formulas on small screens in the web whitepaper #1069))
• Logical operator (\bigwedge, \bigvee, \equiv) render size mismatch ([#1070](Symbol size mismatch in Mintlify render for web whitepaper #1070))

---

[fakela]

@reveloper I have crossed check this by first converting the latex to pdf using this tool: https://cloudconvert.com/tex-to-pdf and reviewing them side by side

[reveloper]

@fakela Could you highlight the diffrences(between webpage render and TeX render) you still notice between these documents but can't be arragned with mintify? It's maybe helpful for further review and improvements.

[fakela]

@fakela Could you highlight the diffrences(between webpage render and TeX render) you still notice between these documents but can't be arragned with mintify? It's maybe helpful for further review and improvements.

Thanks! From my side, the TeX and webpage renders match on code, text, highlighted math expression, and general formatting. I think this is a direct match now.

The one issue I have is with HASH. In the Tex PDF, it renders as: H (regular capital) + ASH (small caps), creating a subtle size distinction. However, in Mintlify/web, I had to use$\text{HASH}$ with all regular capitals because true small caps aren't supported. However when I did conversion from latex to markdown with a claude it kept it as Hash.

(Please let me know what style to use)

This is one of those differences between TeX and web rendering that can't be perfectly replicated

[reveloper]

Let me share extra for possible fixes.

I ignore all link formatting and link addressing during this review, since we should resolve this in a separate update.

@novusnota, @verytactical
I listed the differences with the "need fix" and "ok" checkboxes.
Please help us define what we should or should not fix: mark each as an issue to fix with "need fix" or ignore with "ok".

PS: I marked obvious issues as Need fix by default.

1. The quotes style is different

• Need fix
• Ok

---

2. Different paragraph alining

• Need fix
• Ok

---

3. Spacing before brackets. Seems similar, but PDF version doesn't include space.

• Need fix
• Ok

---

4. Contents page excluded from web version

• Need fix
• Ok

---

5. Number formatted with comma

• Need fix
• Ok

---

6. PDF has a specific styling for variable like CellRepr and SHA.

• Need fix
• Ok

---

7. The visual difference between the italic and the default font in the web page is tiny (example completion tag), so this highlighting is almost unseen.

• Need fix
• Ok

---

8. Minor differences in header formatting: first header sentence changed to ### Header without a dot.

• Need fix
• Ok

---

9. Lost underscore in account_id

• Need fix

---

10. Didn't render to wide dash (within all file)

• Need fix

---

11. Code formatting minor diffrences

• Need fix
• Ok

---

12. Lost ; in the web version

• Need fix

---

13. Dash list changed to a bullet point list

• Need fix
• Ok

---

14. Lost italic formatting for witness

• Need fix

---

15. Lost paragraph spacing

• Need fix

---

16. Lost comma in the 1.3.9

• Need fix

---

17. In the formula ... seems a bit different

• Need fix
• Ok

---

18. In the formula ^-like and V letter seems different

• Need fix
• Ok

---

19. Lost italic formatting in ch 1.3.12

• Need fix

---

20. Lost italic formatting in ch 1.3.16

• Need fix

---

21. LT different formatting within entire document

• Need fix
• Ok

---

22. Formula render doesn't fit in the page in ch. 1.4.2

• Need fix

---

23. Lost . in header name

• Need fix

---

24. Lost italic format for begins and ends

• Need fix

---

25. Lost italic format for final

• Need fix

---

26. Lost italic format for sentence

• Need fix

---

27. Lost italic format

• Need fix

---

28. Lost italic format

• Need fix

---

29. Excluded dots in headers

• Need fix
• Ok

---

30. Lost italic format

• Need fix

---

31. Lost italic format

• Need fix

---

32. Sum symbol format a bit different

• Need fix
• Ok

---

33. List style different: bullet points vs dashes.

• Need fix
• Ok

---

34. Difference in TL-B.

• Need fix

---

35. Number formatted with comma

• Need fix
• Ok

[fakela]

@reveloper, I wanted to point out something for issue 22 and (potentially other related ones), the formula render does fit the page (it shows full on my monitor screen). I'll say the formulas are probably not responsive for smaller screens. This might be something we can bring up with the mintlify team

[fakela]

34. Difference in "Nexthop"

• Need fix
• Ok

36. Difference in "LT" format

• Need fix
• Ok

37. Difference in the "F" format. This "F" format appears in multiple places

• Need fix
• Ok

38. Difference in the "z" format

• Need fix
• Ok

39. Overflow of code due to non-responsiveness in smaller screens

• Need fix
• Ok

40. Overflow of code due to non-responsiveness in smaller screens

• Need fix
• Ok

41. Overflow of code due to non-responsiveness in smaller screens

• Need fix
• Ok

[reveloper]

@fakela
Previously, point 5, uploaded image - wrong.
Numbers formatted with a comma, but should be the same.

[reveloper]

Extra for review

1. ~ seems different

• Need fix
• Ok

---

[fakela]

Extra for review

1. ~ seems different

• Need fix
• Ok

WIP

@reveloper this is what it looks like on the tex file. I think the curl ~ placement is okay

\begin{verbatim}
ahm_edge#_ {n:#} {X:Type} {Y:Type} {l:#} {m:#} 
  label:(HmLabel ~l n) {n = (~m) + l} 
....

[reveloper]

LGTM, the only issue I faced related to SHA/Sha/sha formating, I prefer to fix it later with minor updates. Let's merge this.
@verytactical