Greetings!
I noticed that method POST referred a StackOverflow post, while a recent comment to it mentioned that the files API has been deprecated, and so this answer will cease being valid from then end of July 2015.
I'm trying to learn the usefulness of such small updates on StackOverflow. Would this comment help improve your code? I understand that such defect might not happen in real life situation. In that case, do you think this comment can help prevent future bugs (for example, when the code were reused somewhere else)?
I'll really appreciate it if you could kindly give me some feedback or suggestions. Thank you very much for your time.
Have a nice day!

accept input of pali words in thai, burmese, etc, scripts.

at the top or bottom of word page, show similar words.

Bootstrap responsive design is used to create dictionary website. Need a mobile tipitaka website as well.

Reference:
palipad - Type Pāḷi text in your browser
Demo.

Mahāvaggapāḷi is often used as title of the pali texts, and Mahāvaggapāḷi appears in different places in the canon. So far we cannot give different translated title names of Mahāvaggapāḷi in different places in the canon. Should we support different translated title names of Mahāvaggapāḷi in different places?

The Vnm interface should has full name as: "Tiếng Việt" instead of "Việt"

Thank you!

For example, in webpage of DN 1, link(s) to commentaries, sub-commentaries of DN 1 should be provided if available.

So far, only the first part of the compound is taken into account.

should convert "Sacca" to "sacca" in JavaScript code.

for example, if click [1] in texts, jump to footnote 1 at the bottom of the page.

Design a interface, when users type or click MN 1, show MN 1 and available translations to users.
possible short name (from Access to Insight):
DN, MN, SN, AN, KN, Khp, Dhp,....

server /about page according to http ACCEPT_LANGUAGES header if the url does not start with /{{ locale }}

serve /about page of {{ locale }} language if the url starts with /{{ locale }}

1. Use Pagination: 100 words per page.
2. Use static page: 33 pages for 33 prefix

If special chars like ñ, ṭ, etc. are in the URL, this will cause http 500.
Need to check encoding of the input parameters in URL.

For example, add original translation URL of the translation xml, or copyright information of the translation xml, etc. And still compatible with VRI format.

The notes appear inside the text. They should appear at the bottom of the page.

example: sutta 49

On the Canon site, the main menu's titles are having large space. It should be short space like the Dictionaries site. (For example: "Trang_chính". Not "Trang___chính". This problem has just occured on the Canon site. Not on the Dictionaries site.

Actually, it is a mistake of arrangement when they made the online version.

In the Aṅguttaranikāya >> Ekakanipātapāḷi >> 9. Pamādādivaggo, the paragraph #81 should belong to chapter 8 (Kalyāṇamittādivaggo) instead of current state.

In the Aṅguttaranikāya >> Ekakanipātapāḷi >> 10. Dutiyapamādādivaggo, the paragraphs 130 to 139 should belong to chapter 11 (Adhammavaggo) instead of current state.

In Vietnamese Canon, those paragraphs are put in right chapters.

I sent an email about this mistakes to source site http://www.tipitaka.org/romn/ and waiting for their response.

I agree with Siong-Ui that we should ask people at the source site to fix the problem first, then we update our site.