On Sat, 13 May 2006, Marc Santhoff wrote:
> Am Samstag, den 13.05.2006, 16:20 +0200 schrieb Michael Van Canneyt: > > > > On Sat, 13 May 2006, Thierry Andriamirado wrote: > > > > > Le samedi 13 mai 2006 à 09:57 +0200, Michael Van Canneyt a écrit : > > > > > > > Same goes for docs... I agree that we should make some modifications > > > > for > > > > tranlations, but I don't think that .po files are the way to go... > > > > But that is my personal opinion. > > > > > > But 'many' (all!) translators use .po editors. If apps produced by > > > fpc/lazarus doesn't support .po and .mo formats, they'll never be > > > translated. > > > > FPC itself has support for .po files (see gettext unit) but > > the documentation currently not. > > > > And forgive me: The translator should under no circumstance know > > what the underlying format is, just as the end user of a database > > application should not have to bother with what kind of database his > > application uses. > > > > If we provide good tools for easy translation, things will be translated. > > Whatever the format. > > I do not know, how professional translators would react if one suggests > them using a .po editor for something else than short message strings, > but I *do* now abtracting from format issues and having good tools is > essential. > > One thing frequently asked for is having a side-by-side editor with > syncing and bookmark option. Indeed. This kind of thing I think should be added to the lazarus doc editor... Michael.