In the never ending stream of photos of bad/funny/inventive translations on the internet, I bring you all an example from my latest trip to Russia.
Although my Russian sucks, I think they are telling you to please not throw rubbish in the sink. Anyone know what a "bowlhole" is? I have never seen that word before (or since for that matter).
Thursday, May 14, 2009
Monday, May 11, 2009
TeamCity, Ant & DITA
Over the last few days I have been trying to get a CI server (aka build server) up and running. After trying out both CruiseControl and CruiseControl.NET I landed on TeamCity since it is a bit simpler with a decent web GUI as well as being somewhat familiar from my work.
You can download TeamCity and try it out for yourself since they offer a free edition that supports up to 20 build configurations and 3 build agents.
One of the tasks I wished to accomplish in by CI server was to build the online help files (HTML) as well as the user manual (PDF). Having all the source material in DITA formatted XML files makes that pretty easy from the command line using the DITA Open Toolkit full easy install distribution. Getting it to run automatically from TeamCity proved to cost me some gray hairs though.
So as a note-to-self here is a short checklist of what to do after TeamCity has been installed:
Setting the CLASSPATH environment variable had NO effect, neither had adding -classpath to the JVM command line options. Only adding it as a -cp option to the Ant command line did the trick. I did not find any mention of this in either DITA documentation or TeamCity documentation.
It might be obvious for someone more familiar with Ant, but for me it was a big hurdle I only discovered while (desperately) searching trought the Ant plugin configuration on my TeamCity server.
You can download TeamCity and try it out for yourself since they offer a free edition that supports up to 20 build configurations and 3 build agents.
One of the tasks I wished to accomplish in by CI server was to build the online help files (HTML) as well as the user manual (PDF). Having all the source material in DITA formatted XML files makes that pretty easy from the command line using the DITA Open Toolkit full easy install distribution. Getting it to run automatically from TeamCity proved to cost me some gray hairs though.
So as a note-to-self here is a short checklist of what to do after TeamCity has been installed:
- Download DITA and unzip it. (Ex in: C:\DITA-OT1.4.3)
- Create a new build configuration for you project, and set "Ant" as the "Build runner".
- "Ant Home" should be the ant folder in your DITA installation. (Ex: c:\DITA-OT1.4.3\tools\ant\)
- In "Additional Ant Command Line Options" input the classpath and any options for Ant or the DITA toolchain it spawns.
- Add DITA_DIR environment variable to the build configuration and set it to the folder you unzipped DITA to in step 1.
- Create a build.xml file for your targets and point TeamCity at it.
Setting the CLASSPATH environment variable had NO effect, neither had adding -classpath to the JVM command line options. Only adding it as a -cp option to the Ant command line did the trick. I did not find any mention of this in either DITA documentation or TeamCity documentation.
It might be obvious for someone more familiar with Ant, but for me it was a big hurdle I only discovered while (desperately) searching trought the Ant plugin configuration on my TeamCity server.
Monday, May 4, 2009
Item Assistant v0.9.3
I have just released a new version of Item Assistant. This version fixes bugs, improves performance and cleans up/improves the GUI a bit.
From the changelog:
From the changelog:
Check out the downloads page at sourceforge to grab a copy. This distribution also includes some DLLs that were missing from the previous version and should hopefully fix the problem some people have with it not starting up.
- Added support for NPC trade-in quest rewards in the item tracking.
- Now parsing the 18.0.1 database correctly.
- Find panel now filters on dimension as well.
- Added support for Xyphos.com for item stats/links.
- The report in the Pattern Matcher now links to the loot table for the boss.
- It is now possible to export all items (excluding backpacks) from a toon by right-clicking the toon name in the tree-view.
- Improved performance when ripping the AODB.
- Bug Fix: Identify view will now sort (right hand side list).
- Bug Fix: Toonlist in the find-panel and pattern-matcher should now be sorted.
Subscribe to:
Posts (Atom)