Looking in detail of the text, there are a a a lot of ââ?ââ question marks? Look like where âspacesâ or commas should be. Original site built with MS Office. Tried two FTP clients both same results.
Hi and welcome to the community! This might be an encoding issue. Your charset appears to be Windows-1252 (probably the default). Depending on the application and version you are using for editing the web page on your Windows desktop, select File â Export âPublish HTMLâ Advanced OptionsâEncoding âUnicode (UTF-8) â OK.
Re-upload your files using FTP and overwrite the old ones in htdocs. Kindly verify by opening a new incognito window on your browser if the changes took effect.
I havenât used Word in over a decade myself, but according to this article, you should get a File Conversion dialog box after choosing the export file type:
Alternatively, you could also try opening the HTML file with a text editor after saving it to re-save it with UTF-8 encoding, but thatâs going to get cumbersome if you need to do that any time youâre updating your website.
I will read through the Microsoft Support link suggested. Just looked up the MS Word version I used putting the original Norcim site together and it is quite old, Version 2013.
The Norcim site has been uploaded a few times to previous hosting sites in the past with no apparent problems. So this quite minor text oddity is a new one.
The real good thing about âInfinity Freeâ is, itâs not only free but comes with an SLL certificate. Much of the content of the Norcim Website is now 50 years old (vintage?) so visitor numbers very likely, few, not worth spending money on. Gives me something to do !
MS seems to be moving and renaming things through the years. The closest here is Office 2010. It is off by a handful of years, but should be near likely: File â Save As â Tools â Web Options â Encoding â Unicode (UTF-8) â OK â Save.
Your site is quite large, so if each one has â?â, it will take a while to finish. There is an automated way but it will require installing (probably) new applications. Seeing you to get it done soon. Cheers!
Well siglo_ph and all involved, Many Thanks for looking into this problem. I appreciate your time involved. But it does look like a not so easy problem to put right.
Infinity Free hosting with its SSL would have been an ideal choice for the old Norcim Website. There are better website builders now than the MS Word for web.
Hello again, and for Technical interest only ! the same MS Word ânorcimâ website has been uploaded without problems to another free hosting site. But there is no SSL certificate and it seems that it is not possible to use a free âadd-onâ SSL version. (you have to go for a paid hosting plan).
Hello Greenreader9, thanks, do you mean a free SSL from the control panel of the scienceontheweb.website (for norcimradiocontrol) ? Must admit I have tried that and it comes up with a payment of around ÂŁ32.00. ??
scienceontheweb.net seems to be a different free hosting provider, and they provide free subdomains under their own domain.
That means that (just like our free subdomains actually), that domain is stuck with that hosting provider, so youâre forced to accept their features and plans. So if they charge 32 GBP to get SSL, then thatâs what you have to pay to get SSL on that website.
We donât charge for SSL at all. But that means you wonât be able to use your scienceontheweb.net name. Youâll need to use one of our free subdomains instead.
If you purchase your own domain name, you can freely move it across hosting providers, but purchasing a domain name costs money.
Hello admin again. Thanks for explaining that. Infinity Free was definitely the best place to to upload the old Norcim Website, But it seems that the way it was originally built using âMS Word for webâ does not allow a clean upload to âInfinity Freeâ.The text of the pages get contaminated during upload. Looks like a difficult one to fix.
For sure, every one has moved on. But Iâm revisiting this for technical completeness and future reference. Recreated the dilemma and pondered if there is really a possible way for us, users, to simply put it, just upload and forget. There are solutions already available but all require significant effort, familiarization, or tinkering directly the server files. This is an attempt given with only the limited tools available and the least amount of modification to existing source files.
Assumptions:
User environment and saved files are set in Windows-1252. I have forgotten how MS is the most popular in the world.
Other forums from Google give slightly different variations but this appears to be the most fitting.
Caveats:
For consistency and prevent possible more problems, user needs to edit files in the local Windows-1252 environment ONLY and never online. There is always the danger of mixing charset types.
FTP (terminal) and File Manager (new3) display â?â and other funny characters when viewing files.
However, the downloaded copies from FTP (terminal) and File Manager (new3) retained their windows-1252 encoding and original characters despite the weird display while viewing in IF server.
(This is a downloaded copy from IF via FTP; viewing locally on a browser perfectly now without Repair Text Encoding)
The view-source of the server pages from the browser will display exactly what the client is seeing.
As shown, sample size is very small and very limited and not the original entire site where other issues might still exist.
Final thoughts:
Itâs mostly probably likely possible in InfinityFree after all!