Sometimes, when the contents of a .tex is copied from .docx file, its own encoding might not fit your expectation and cause problems as you compiling it. One way to convert the file to the encoding you want is to use WinEdt: when "save as" a different file, you can have several choices.

closed as off-topic by Schweinebacke, Troy, ChrisS, Stefan Pinnow, Andrew Swann Dec 29 '17 at 12:14

  • This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    utf-8 isn't a font encoding, it is the encoding of the tex file source, as written by the editor, If you have copied text using the windows clipboard it will (usually) be pasted using the encoding of the file that you are pasting to, so it doesn't matter what encoding was used in the source (but most likely they are both utf-8 anyway) – David Carlisle Dec 21 '17 at 22:59
  • 1
    If your editor is not capable of dealing with your encoding, delete it and install a better one. – Skillmon Dec 21 '17 at 23:25
  • @DavidCarlisle It is a fact that when my friend trying to compile my .tex file with her WinEdt, she always gets a warning saying that "Some characters were lost while converting from UNICODE to CP 0. – King Chung Lo Dec 22 '17 at 1:19
  • 2
    so if some characters are lost then you are processing different files so it is not surprising that the output is different and miktex/texlive and package differences are not relevant. Your friend should just configure winedt to use utf8 encoding not a legacy code page on the file. – David Carlisle Dec 22 '17 at 1:50
  • 3
    I'm voting to close this question as off-topic because it is not a question but a kind of statement or how-to or blog. So is cannot be answered. We could only discuss it, but this is not a discussion forum. – Schweinebacke Dec 29 '17 at 9:45