And I guess that saves me having to upload and download the Word files. That is also another sort of acceptable alternative if there isn’t anything more straightforward. Then if I double-click on it it will open in Chrome and look fine. Going via Google Docs is one of the only things that fixes it.Īnother round-about fix is to edit the garbage-looking file, replace all line endings with I usually use BBEdit, but selecting different languages doesn’t seem to fix the contents.
#Bbedit 8 download how to#
Like even figuring out how to fix the encoding on my Mac and open it with just an ordinary text editor. I’d like to be able to select all 100, save all 100, then download all 100 and be done with it but I can’t. This would be ok if not for the fact that in Google Drive you can only open one file at a time. So Google Docs is able to figure out what the encoding or whatever issue there is and fix it.īut if I try to not use Google Docs (it’s an extra 100+ steps to go that route) and open them directly with Word on my Mac it just causes a bunch of errors and they won’t open.
If I save them as Google Docs and download them to my Mac as Word files they look fine on my Mac when I open them with Word. If I open them in Google Docs they look fine. If I upload the files to my Google Drive and open them in Preview there they look fine there. txt and open them they look like garbage. If they were UTF-8 there probably wouldn’t be this problem. I think they might be ISO-2022-JP encoded but I’m not sure. I’m creating about 100 text files on a server. I wonder if any techie here can give me a suggestion.
0 kommentar(er)
