Blog

Luis Majano

October 15, 2008

Spread the word


Share your thoughts

This is an announcement that an internationalization translation project is way on its way for the ColdBox documentation. If you go to the official wiki site, you will see two new languages: Japanese and Spanish. The entire docs are being translated now to these languages and should be done by version 2.6 release if possible. Also, a new group has been created for ColdBox Translators. So if you are interested in helping out in the translation process, become an official translator or just help out, please email us at info@coldboxframework.com. Right now we have one Japanase translator and one Spanish translator. So please contribute if you have time.

Add Your Comment

(2)

Nov 26, 2009 11:41:55 UTC

by Marcelo Santana

Estimado Luis, estoy migrando desde Fusebox y me gustaría acceder a la documentación en español, así como tratar de contribuir a su traducción, pero al parecer ahora no es posible visualizarla. Es posible reestablecer el enlace o que me envíes lo que exista de documentación en español?

Gracias.

Feb 18, 2010 23:24:50 UTC

by Luis Majano

Marcelo, disculpa la tardanza en eso. Mandame un email a lmajano@ortussolutions.com para que charlemos sobre como pasar documentacion en español

Recent Entries

Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Reasoning-capable models have been usable in BoxLang AI for a while. params passes straight through to the provider body, so params: { thinking: { type: "enabled", budget_tokens: 10000 } } for Claude, or params: { reasoning_effort: "high" } for OpenAI, already reached the API. What never worked was reading the reasoning back. It was parsed out on arrival and silently dropped. In 3.4.0, that's fixed, and it's fixed the same way for every provider.

Luis Majano
Luis Majano
September 15, 2026
BoxLang 1.17 Series Part 4 : WriteDump Enhanced!

BoxLang 1.17 Series Part 4 : WriteDump Enhanced!

You call writeDump() on an ORM entity or a very rich class graph . The browser locks up. Thirty seconds later you get a page with forty thousand rows on it, you scroll for a while, you give up, and you go edit your code to dump a sub-key instead. Or worse, you crash the server.

Luis Majano
Luis Majano
September 11, 2026