June heat has been slowing down development somewhat in Budapest, and this month was heavier on backend improvements and preparation work than it has been on new features being rolled out to the UI. Still, we did manage to complete a few new things, such as wiring up the Client-side Translation feature on the UI (still in beta), rolling out the ability to override content types before translation, and a new crawl interface that allows even more configuration options. See the full details after the jump!
Content Type Override
Do note, however, that in order to maintain compatibility, all content types must be specified exactly (i.e. pattern matching, globbing, or prefix rules are not supported in the map)!
New Crawler Interface
The crawl dialog has also received a rather large facelift, with many new options being added.
For instance, you can now disable the processing of <img src> attributes during a crawl. This is most useful when discovering a large site with many images for word count purposes, before the content extraction crawl. By forgoing the processing of images, the number of requests sent (and therefore the time taken) is reduced greatly.
It is now also possible to put a throttle on the crawl by setting the number of simultaneous requests. By default, the proxy sends out eight parallel requests at most, which is also the upper limit of this setting. However, if the server responds with “Too many requests“, you can dial the load back by decreasing this value.
Stay tuned for more interesting features to make website translation easier!Dedicated demo for You Tweet