- Suppose the grade of students are stored in A1:A70.
- Bin array (B1:B11) stores 9, 19, 29, ..., 99, 109.
- Grades <= 9 falls into the first bin.
- 10 <= grade <= 19 falls into the second bin.
- The last bin is for 100 <= grade <= 109.
- Create an array C1:C11 which is =B1-9. This will be the x-axis for the bar chart.
- In D1, Enter the formula =FREQUENCY(A1:A70, B1:B11).
- You will get 12 cells. The additional bin is for 109 < grade. The value is certainly 0. You don't include this in the bar chart.
- Draw a bar chart with C1:D11.
2025年4月22日 星期二
[Excel] Drawing Histograms with =FREQUENCY()
How to Create a Histogram in Excel with Two Sets of Data
2025年3月26日 星期三
Expand Acronyms in MS-Word
File - Options - Proofing - AutoCorrect Options
Replace text as you type
(e.g., replace "sip" with "Session Initiation Protocol")
2022年5月19日 星期四
Default Font of PPT Objects
https://answers.microsoft.com/en-us/msoffice/forum/all/default-font-for-ppt-objects/a081100d-76fd-4367-abe9-085c70966893
If you want to set the default font size or background color of text boxes or callouts:
- View - Slide Master - Insert Layout (This will create a custom layout.)
- Home. Create a textbox. Change the font size and background color.
- Right-click the text box and choose "Set as Default Text Box".
- Create a callout and change its font size or background color as you wish.
- Right-click and "Save as Default Shape".
- Slide master - Close Slide Master.
2019年1月14日 星期一
2018年12月28日 星期五
12 Tips to Speed up Windows 7
https://www.pcmag.com/feature/251692/12-tips-to-speed-up-windows-7
11. Don't Use a Beautiful Desktop Background
Personalize - Desktop Background - choose a solid color (e.g. Black).
12. Turn Off Aero Effects
Control Panel - Performance Information and Tools - Adjust Visual Effects - Adjust for Best Performance (this will turn off everything).
2018年1月28日 星期日
Convert UTF-16LE to UTF-8
Jack Jr. reported an interesting problem: Under
manager@ms14:www/secure, he tried to add an RCS keyword $Date$ to
index.htm, hoping that RCS will automatically update the modified time.
However, it did not work. The string was not replaced. What puzzles him is, when he created a new file for testing, everything works fine.
Let us inspect the checked-out index.htm file. When you edit it by vim, on the status line you see "[converted][dos]". The message "[dos]" simply indicates that this file was created in DOS/Windows environment, where newline characters in text files consists of CR+LF (\015\012). On the contrary, in Unix newline characters are a single LF. However, this is not the cause which prevented RCS to work properly.
Let's inspect the contents of index.htm, with a better tool. 工欲善其事,必先利其器. You may use the "dump.cpp" program you developed in the VoIP class, which we adopted to inspect WAV files. You may also use a Unix command "od -t x1 index.htm" to inspect each byte. Now you should see the problem. Each character is stored as two bytes. The ASCII code of the string "Date" is "44 61 74 65", but it was stored as "44 00 61 00 74 00 65 00". That's why RCS failed to recognize this keyword.
By inspecting the beginning of the index.htm file, we see "FF FE", which is BOM (byte order mark, https://en.wikipedia.org/wiki/Byte_order_mark). By checking some article (https://unix.stackexchange.com/…/process-a-file-that-starts…) we learned that this indicates that the file is encoded in UTF-16, little endian!
So the solution should be simple. We need to convert this file from UTF-16LE to UTF-8. Let's type the command "mv index.htm index.bak; iconv -f UTF-16LE -t UTF-8 index.bak > index.htm".
Before we check-in the new UTF-8 file, please inspect its size. You can see that its size is almost half of the UTF-16 file. Now check in and check out index.htm. The converted file works fine with RCS keywords now.
However, it did not work. The string was not replaced. What puzzles him is, when he created a new file for testing, everything works fine.
Let us inspect the checked-out index.htm file. When you edit it by vim, on the status line you see "[converted][dos]". The message "[dos]" simply indicates that this file was created in DOS/Windows environment, where newline characters in text files consists of CR+LF (\015\012). On the contrary, in Unix newline characters are a single LF. However, this is not the cause which prevented RCS to work properly.
Let's inspect the contents of index.htm, with a better tool. 工欲善其事,必先利其器. You may use the "dump.cpp" program you developed in the VoIP class, which we adopted to inspect WAV files. You may also use a Unix command "od -t x1 index.htm" to inspect each byte. Now you should see the problem. Each character is stored as two bytes. The ASCII code of the string "Date" is "44 61 74 65", but it was stored as "44 00 61 00 74 00 65 00". That's why RCS failed to recognize this keyword.
By inspecting the beginning of the index.htm file, we see "FF FE", which is BOM (byte order mark, https://en.wikipedia.org/wiki/Byte_order_mark). By checking some article (https://unix.stackexchange.com/…/process-a-file-that-starts…) we learned that this indicates that the file is encoded in UTF-16, little endian!
So the solution should be simple. We need to convert this file from UTF-16LE to UTF-8. Let's type the command "mv index.htm index.bak; iconv -f UTF-16LE -t UTF-8 index.bak > index.htm".
Before we check-in the new UTF-8 file, please inspect its size. You can see that its size is almost half of the UTF-16 file. Now check in and check out index.htm. The converted file works fine with RCS keywords now.
訂閱:
文章 (Atom)