When you first launch TextEdit, you get the familiar dialog box where you can select an existing text file to open.
This reveals a section that says Plain Text Encoding with a very unfamiliar list of encoding options, allowing you to choose which character encoding you'd like to use.
But if you ever open a text file and it appears garbled or uses, you know, incorrect characters, you can manually select the correct encoding from this menu before opening the file.
By default, encoding is set to automatic, which means it'll try to figure out how the text file was encoded.
Still, on this open window, there's another option that might be more useful.
If you uncheck ignore rich text commands, then you'll see the raw HTML in the document where you can edit it.
I opened the index.html file for my web-based time shifter clock, you know, at timeshifterclock.com.
And you can see a small smidge of formatting, like the title is bold and there's a few elements that have the correct colors.
But TextEdit doesn't have any of the bootstrap goodness that went into making them actual buttons.
Opening the same index.html file with the checkbox selected to ignore rich text commands opens the file showing all 279 lines of code.
Now, it's interesting to me that the default is to have this box unchecked because I'd be more likely to use TextEdit to edit a raw HTML file than try to use TextEdit as a web browser.
The good news is you can toggle this behavior in settings so the raw text opens by default.
TextEdit defaults to creating what's called an RTF document, which stands for Rich Text Format.
When you first launch TextEdit, you get the familiar dialog box where you can select an existing text file to open.
This reveals a section that says Plain Text Encoding with a very unfamiliar list of encoding options, allowing you to choose which character encoding you'd like to use.
But if you ever open a text file and it appears garbled or uses, you know, incorrect characters, you can manually select the correct encoding from this menu before opening the file.
By default, encoding is set to automatic, which means it'll try to figure out how the text file was encoded.
Still, on this open window, there's another option that might be more useful.
If you uncheck ignore rich text commands, then you'll see the raw HTML in the document where you can edit it.
I opened the index.html file for my web-based time shifter clock, you know, at timeshifterclock.com.
And you can see a small smidge of formatting, like the title is bold and there's a few elements that have the correct colors.
But TextEdit doesn't have any of the bootstrap goodness that went into making them actual buttons.
Opening the same index.html file with the checkbox selected to ignore rich text commands opens the file showing all 279 lines of code.
Now, it's interesting to me that the default is to have this box unchecked because I'd be more likely to use TextEdit to edit a raw HTML file than try to use TextEdit as a web browser.
The good news is you can toggle this behavior in settings so the raw text opens by default.
TextEdit defaults to creating what's called an RTF document, which stands for Rich Text Format.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.