Problems with translating RB - a design shortcoming
Hi,
I have translated my version of ReportBuilder but now I have problem with
the text of many captions not fitting into corresponding components' space.
Even original English captions often doesn't fit and are truncated on your
forms and I think it should be a rule that you leave at least 40% of
additional space for translated strings because the appropriate strings in
other languages can be much longer. I don't need to customize any of the
forms for now but I want to have nice descriptions after the work of
translating. Having to fine tune all that places after each new release of
RB is a horrible prospect for me.
Thank you
Janusz
I have translated my version of ReportBuilder but now I have problem with
the text of many captions not fitting into corresponding components' space.
Even original English captions often doesn't fit and are truncated on your
forms and I think it should be a rule that you leave at least 40% of
additional space for translated strings because the appropriate strings in
other languages can be much longer. I don't need to customize any of the
forms for now but I want to have nice descriptions after the work of
translating. Having to fine tune all that places after each new release of
RB is a horrible prospect for me.
Thank you
Janusz
This discussion has been closed.
Comments
were stored in a delphi file that purely contained resourcestrings so that
the job of doing translations ( like the one you did ) would become trivial.
In fact if they did store them in outbound files it would be easier for
people like you to just translate it once and send it to them and then from
that point on it would just be included in their release ( or available on
their website [grin] ). It wouldn't take much programming.
Maybe if you did it this way and sent it to them they could integrate your
changes into the real release.
Nice thought isn't it [grin]
application from English to Spanish. After some thought I chose to write TWO
separate reports (each in separate, dummy forms): one in English and the
other in Spanish. It's not very efficient (memory-wise) but it works very
well.
Best regards,
Ray
Thank you
Janusz
application so translation is not so big problem - one can modify easily
*.rc file, compile it, copy to system folder - and that's all. The problem
for me arises later, when my translated strings often turn out to be too
long to fit into, for instance, the relevant labels so I have to localize
the form, the label and in the end to change its size so that the whole
translated strings were visible. The sizes of labels etc. should be simply
set with some reserve because in average English words are shorter than
German, Polish, French etc. words.
Thank you
Janusz