Yuiry,
Here is what I was thinking about for the glass scale incremental interface.
http://www.avagotech.com/docs/AV02-0096EN
For those in a hurry there is already a shield available ...
http://www.robogaia.com/two-axis-encoder-counter-mega-shield-version-2.html ... but I would prefer to make a shield with two IC's on it to accommodate 4 axis. The IC's are about $11 each and they can share the same TTL crystal oscillator so a home-made shield might come in under $30, and certainly under $50 if it were made it on a ready-made shield breadboard.
I think they could be made to work in one of two ways ...
In both solutions the Arduino polls the HCTL-2032's [I am assuming there would be two IC and therefore four counters for a three or four axis system] to retrieve the four bytes of 32bit counter information from each of the axis.
One solution would then have the Arduino convert the 32bit information into the format that is currently being used to transmit data to the Android tablet, giving the impression that the iGauging scales were being used, albeit with some pretty outrageous value.
The other solution, and IMHO the better one, would be to allow a second format where the coordinate information would be a hex representation of the 32bit counters. The conversion from the hex values to what ever the Android is using internally ... Big Decimal, Floating Point, what every ... is then done by the is then all done inside the Android tablet. The values would still be outrageous but I do not think the Android cares as, if I am not mistaken, you said it is simply thinking in incremental terms anyway.
Obviously I have spent all of 30 seconds on the analysis, but at least that is where I would start.
Arvid