FWIW The documentation does not use markdown syntax, but asciidoc. Den fre. 13. jul. 2018 kl. 23.52 skrev Wayne Stambaugh <stambau...@gmail.com>: > > If the wxHtml widget would support markdown that would work but I don't > think that is the case. I prefer converting it to markdown and moving > it into the Eeschema user documentation. It's currently not in the > documentation so that is an issue itself. It's something we should > definitely take a look at both in terms of the documentation and the > lack of translation. > > On 07/12/2018 11:36 PM, David Godfrey wrote: > > Hi Wayne, > > > > Out of interest, if formatted translated text is required in this > > dialogue would it be easier to change from html to markdown? > > > > At least markdown is fairly easy for a translator to work with, although > > it doesn't provide all of the flexibility of html. > > > > Regards > > David Godfrey > > SB Tech Services > > mb: +61 437 286 200 <tel:+61437286200> > > > > chat: with /dcg_mx/ at > > #sbts:matrix.org <http://riot.im/app/#/room/#sbts:matrix.org> (Computer) > > #sbts:matrix.org <http://matrix.to/#/#sbts:matrix.org> (mobile Device) > > > > > > On 12/07/18 22:15, Wayne Stambaugh wrote: > >> On 7/12/2018 8:59 AM, Simon Richter wrote: > >>> Hi, > >>> > >>> On 11.07.2018 21:51, Wayne Stambaugh wrote: > >>> > >>>> This probably should have been done as a cpp string wrapped with the > >>>> translation macro _(). I'm not sure there is anything we can do to make > >>>> this translatable. Anyone else have any ideas? > >>> We could move the entire text to the user documentation, and make the > >>> dialog point at it. > >>> > >>> If the dialog is unusable without the documentation, then that is a > >>> separate problem, but I doubt it's that bad. > >>> > >>> Simon > >> I completely missed the fact the html file is converted to a C string by > >> Html2C.cmake. It would be easy enough to modify Html2C.cmake to wrap > >> the string with the _() macro. The problem I see is the string (see > >> generated file eeschema/dialogs/dialog_bom_help_html.h) has a lot of > >> markup which I'm sure will make life miserable for translators. > >> > >> We could try Simon's suggestion of moving the html text to the eeschema > >> user docs and provide a link using the help button. We would have to > >> add code to point the help url to the translated version if it exists > >> but that shouldn't be too difficult (famous last words). The contents > >> of the BOM dialog html file do not appear to exist anywhere in the > >> eeschema user doc. > >> > >> In the future we should refrain from doing this so that all source > >> strings and documentation can be translated. > >> > >> Wayne > >> > >> _______________________________________________ > >> Mailing list: https://launchpad.net/~kicad-developers > >> Post to : kicad-developers@lists.launchpad.net > >> Unsubscribe : https://launchpad.net/~kicad-developers > >> More help : https://help.launchpad.net/ListHelp > >> > >> > > > > > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~kicad-developers > > Post to : kicad-developers@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~kicad-developers > > More help : https://help.launchpad.net/ListHelp > > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp