txt extension forces Excel to run the Text Import Wizard): iconv -f UTF-8 -t UTF-16LE filename.csv >. defaults write AskForUnguessableFileEncoding -bool YES. And older web browsers don't understand Unicode.Is what I am saying true? Any advice on which method to use?A side question - to give an example of the issues I am trying to avoid, I am talking with the webmaster of the site that has this page: page shows some special characters (like smart quotes) as "undisplayable" characters on my Macintosh when I use Safari. The following worked for me on Excel for Mac 2011 and Windows Excel 2002: Using iconv on Mac, convert the file to UTF-16 Little-Endian + name it. windows (or ignore them when filtering for text files). The disadvantage is that a web browser that doesn't understand Unicode will display characters incorrectly. The disadvantage is that when I edit the webpage, especially in French, I see a lot of HTML named entities like eacute which makes it hard to read the text when I am editing in "HTML source" view.Method 2 has the advantage that the document will be saved without the HTML named entities, so it will be easier to read and edit the text when I am editing in "HTML source" view. No need to worry about remembering to translate the non-ASCII characters before I save my changes.My understanding is:Method 1 has the advantage that since all the text in the HTML page is ASCII there will be no compatibility problems with other web browsers or operating systems. EditPlus is a text editor that works on Windows. I need to do this any time I edit the document and add non-ASCII characters.2) I believe that I could also set the document character set to Unicode (UTF-8), which means that BBEdit puts this in the head section:meta http-equiv="content-type" content="text/html charset=utf-8"Then I wouldn't need to translate any of the characters, just save the document, BBEDit would save it as a Unicode document, and it should show correctly. BBEdit will now honor the extended file attribute, if present and appropriate. It is customizable but still easy to use the default configuration. The page is mostly edited with BBEdit.I know of two options that I think should work.1) I set the page's character set to Western (Mac OS Roman) in BBEdit, which means that BBEdit puts this in the head section:meta http-equiv="content-type" content="text/html charset=macintosh"Then I use the BBEdit menu item Markup->Utilities->Translate and choose to use HTML Entities, encode all Unicode characters with an HTML named entity. ![]() This will apply to non-ASCII typographical characters like smart quotes, and also to western european characters like e with an acute accent.I am using BBEdit, Nvu and an old version of Dreamweaver on the Macintosh. BBEdit is the leading professional text, code, and markup editor for the Macintosh. ![]() It is in french/english (each page has a french version and an English version.) I am wondering what is the best way to code non-ASCII characters so that they show up correctly regardless of the user's web browser. Lade BBEdit für macOS 10.15.4 oder neuer und genieße die App auf deinem Mac. I a still a novice at HTML, so excuse any technical errors in my post.I am working on revamping my personal website.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |