You’ve probably noticed already how Spin Rewriter knows to be extra-helpful by showing your local times next to your spun articles inside the Archive.

It doesn’t matter whether you’re from LA, NYC, London, Moscow, Beijing, Tokyo or Sydney… or any tiny little village in between… the times shown will always be your very own local times to make things super easy for you.

Well, with one tiny exception until now… There’s a few short time periods throughout the year where different timezones switch to daylight saving time a couple of days before other timezones, OR when certain timezones stop using daylight saving time just a bit earlier than the others. And then there’s Arizona where they just don’t care. 😀

Anyway, in some of these short overlaps, your local times could be off by 1 hour in some cases. Nothing too horrible, but then again, that’s now that we’re all about here at Spin Rewriter. We’re always striving for perfection — and when it comes to time localization, we’ve just delivered that perfection with an update earlier today.

Enjoy! 😀

In my previous post I already mentioned how we’re rolling out some minor tweaks and fixes for various edge-cases when it comes to automated processing of original texts before our ENL Semantic Spinning algorithms begin their work.

Now, in some extreme cases our processing algorithm could sometimes get confused when it encountered the “<” sign because it thought that maybe it signifies the beginning of an HTML tag. All HTML tags begin with “<” and then usually end with either “/>” or another “>” immediately after the name of the tag.

Here’s an example of what used to cause a problem for our parser:

Mathematicians sometimes use p < 0.01% to signify low risk.

This would in some cases (depending on the context) turn into:

Mathematicians sometimes use p (the rest of the sentence is missing)

…after the Step 1 processing because our parser mistakenly took the “< 0.01%” as a malformed HTML tag instead of what it truly was.

Well, it certainly doesn’t do that anymore — we just fixed this issue, and rolled the update out to our production servers! 😀