Converting Repeating Decimals
You just multiply the decimal by enough powers of 10 to line up the repeating parts, subtract, and simplify. That's the whole process. It's been around since long before calculators could handle it, and it still works the same way. Take something like 0.3333... You know that's 1/3 without doing any math. But when it's not such a clean number, you do this: let x equal the decimal. Multiply x by 10 raised to the power of however many digits repeat. Subtract the original x from that result. Whatever's left over is the repeating part eliminated, and you solve for x. For example, with 0.121212..., x equals 0.121212..., and 100x equals 12.121212.... Subtract them and you get 99x equals 12. Divide both sides by 99 and you reduce 12/99 down to 4/33. That's it. The denominator is always a string of 9s equal to the repeating digits, with some 0s tacked on if there are non-repeating digits in front.
I remember running into a problem a few years back where someone gave me 0.0454545... with the repeating part starting after a zero. The quick answer most people give is to treat the entire thing as repeating and use 99 in the denominator, but that gives you the wrong answer because you're ignoring the leading zero that doesn't participate in the cycle. The workaround is to split it. Write it as 0.0 plus 0.0454545..., convert the repeating chunk 45/990, and add them. Or more cleanly, let x equal 0.0454545..., multiply by 10 to get 10x equals 0.454545..., then multiply by 100 again for 1000x equals 45.454545..., subtract to get 990x equals 45, and reduce from there. The key insight is that the multiplier has to account for every non-repeating digit before the repeat starts, not just the repeating portion. Here's something people commonly miss: the repeating part doesn't have to start right after the decimal point. With 0.1666..., the 6 repeats but the 1 doesn't. If you apply the naive method and assume everything after the decimal is repeating, you'll get 16/99, which is wrong. The correct approach is to separate the non-repeating 1 from the repeating 6. You get 1/10 plus 6/90, which simplifies to 3/18 plus 1/18, giving you 4/24, then 1/6. Check it: 1 divided by 6 is 0.1666..., which matches. The denominator here is 6, not 99, because the repeating digit count is just one. Another thing that trips people up is when the repeating block contains zeros. Take 0.101010..., where the repeating block is 10. The denominator is 99, not 9, because two digits are repeating. Some people see the zero and think it cancels out or changes the rule. It doesn't. The length of the repeating cycle determines the number of 9s, period. Whether the digits are 10, 01, or 99 makes no difference to the denominator structure.
When This Approach Falls Apart
The algebraic method works fine for simple repeating decimals, but it becomes messy fast with mixed repeating decimals that have long non-repeating prefixes. Take something like 0.1234567890123456789..., where you have a 9-digit non-repeating section and a 10-digit repeating section. You'd be multiplying by 10 to the 19th power, dealing with enormous numbers, and the arithmetic gets prone to transcription errors. I've seen people waste twenty minutes on problems like this when a spreadsheet or a quick script would handle it in seconds. There's also the edge case of decimals where the repeating part is extremely long. Some fractions produce repeating cycles of dozens or hundreds of digits. Converting those by hand is theoretically straightforward but practically painful. In those situations, you're better off using the continued fraction approach or just running it through a tool. The theoretical foundation is identical, but the execution is different. If you're doing this repeatedly, the manual method will slow you down. I keep a small Python script on hand that takes any repeating decimal pattern and spits out the reduced fraction in under a second. It handles the edge cases I mentioned above without needing me to think through each one. For occasional use, the hand method is fine. For anything involving multiple conversions or long repeating blocks, automation saves real time.
Get the Full Details
