The Web Log

The Problem Suppose you have created an HTML page with a table and some data in it, and now you want to work with that data in Excel. Well, the good news is that Excel can open the HTML page and automatically parse the HTML and convert it into an Excel spreadsheet. Your data table will be automatically populated in Excel cells. The bad news is that if you have a cell with only numbers in it, for example, a serial number with leading zeros, like this: 000245689 . Excel will format it as number and remove the leading zeros. You will then have to add back the leading zeros and format it as text to preserve the leading zeros. However, not only it's a hassle having to add back the leading zeros, but it's not always possible to know how many leading zeros were in the original number, if you have 100 numbers with leading zeros all with different lengths. You could check the original HTML 1 by 1 but it's very time consuming. The Solution Well, it turns out...

A pussy cat overwhelmed by the amount of food available.

 

Most programming languages use comma separated arguments in their functions, like this: someFunction(arg1, arg2, ...) However, depending on your region and number format settings, Excel may choose to use semicolon instead. This is because Excel is trying to interpret comma as decimal separator, and so it decides to use semicolon for argument separator. This can be extremely frustrating for people who are used to programming languages having comma as argument separator in functions. In this tutorial, I'll show you how to change Excel to revert back to using comma as function argument separator. Note this tutorial is tested on Excel 2019 but may work with other versions as well. Excel Options Open the File menu and click on Options . (I hope you know where the File menu button is...) In the Excel Options interface, click on Advanced , then under the Editing options section, you should see 3 settings: Use system separators Decimal separat...

Construction workers take turns on hot girls gone wrong.

Discovered - currently not indexed If you have a lot of pages in your Google Search Console that are excluded, you might find that a lot of them are Discovered - currently not indexed . And if you drill down by clicking on it, you will find that Google did not even crawl these pages as their last crawled date is all N/A : The explanation given by Google is that google bot may have encountered problem trying to crawl the page. I find that highly unlikely, though, as my site has barely any traffic, and it's hosted on Blogger - Google's own service. A more likely explanation is that, for whatever reason, Google deemed these pages are unimportant, and put them very low in the crawl queue, and since Google bot is quite busy, it never got around to crawl these pages. How does Google determine which pages are important since it never even crawled them? I have no idea. Maybe it just looked at the title, or maybe it did a quick word count. Man...