@C0deDaedalus, I just tried to make that question self-contained so that readers didn't need to go read the link to understand the relevant content.

"tips for how to better edit questions from your experience." Well technically, it would have to be from your own experience. :-) But I'll take a shot. Some brain vomit on editing.

You'll pick up what makes a good post. A lot of it is "knowing it when you see it". If you know what a good post should look like, it's easier to recognize what needs fixing.

There's some good generic guidance in the Help and various Meta threads on what makes a good question or answer, like How do I ask a good question?), What is required for a question to be 'high quality'?, How do I write a good answer?,

How do you write a Stack Exchange answer?, and What are guidelines for reviewing?.

The more you write, yourself, the more adept you will get at it, and the better you will become at being able to improve someone else's writing. Take seminars in technical writing and writing in general. Write as much as you can and have good writers or editors copy-edit your work so you can learn from it.

There are a number of good writers on this site. Pay attention to posts that stand out to you as being really well written. Read other posts by the same authors. You will develop a feel for a "good" post. That will make it easier to spot posts that aren't as good and to recognize why they aren't as good. Try to improve whatever isn't as good (which may require asking the OP for clarification).

There are some limits to editing, though. The focus is more on problem solving than polishing for publication. The goal is to have questions that are understandable and unambiguous, that people will read and answer, and answers that are understandable. Edits should solve obvious English problems (typos, spelling, grammar, punctuation, capitalization, etc.), readability problems (formatting, organization, wall of text, bad writing, etc.), and clarity problems.

Fix "compliance" problems, like proper attribution.

Changing technical content is generally out of bounds for an edit. Adding supplementary information, like to expand or update a post, shouldn't stray into tangential information that the OP didn't intend to cover, and it may be appropriate to identify content that is yours so you're not putting words in the OP's mouth.

Edits to questions that are on-hold or closed need to solve the closure issue (the edit puts the question into the reopen review queue and you don't want to waste the time of many reviewers on inconsequential changes to a closed question).

A grey area is when the edit gets into just polishing the OP's writing (the OP should retain ownership of their own words as much as possible). I usually ask the author's permission before doing that, or restructuring the OP's organization to make it easier to follow.

As far as not getting the comment, do you mean "including how having "utf8 support" translates to "how to have utf8 support"? You had said "You need to have indic fonts installed and utf8 support for them as well." The fonts are obvious, you install the fonts. But what does the OP need to do to have utf8 support? :-)

@fixer1234 Thanks @fixer1234, for every word. I shall make a note out of it. Just one last thing, May I have your email address please ?

@C0deDaedalus, I purposely post anonymously. Unfortunately, I don't have an anonymous email account.