Use JSON call to get the help topic

Also upped the z-index of ui-dialog in admin theme because help text fell behind top banner
Sorry, I forgot about translations. I'll happily remove the markup from 
the messages but would need a steer on what to do with the translations, 
alternatively I could just revert to the original markup (which didn't 
work in this instance - hence the change) What's your preferred 
solution?

Regards
David
Please consider the environment before printing this e-mail



------ Original Message ------
From: "Greg Roach" <notifications@github.com>
To: "fisharebest/webtrees" <webtrees@noreply.github.com>
Cc: "David Drury" <david@drury.me.uk>
Sent: 09/07/2014 03:22:19
Subject: Re: [webtrees] Use JSON call to get the help topic (#197)

>In help_text.php:
>
> > @@ -1014,7 +1012,7 @@ > > case 'USE_SILHOUETTE': > 
>	$title=WT_I18N::translate('Use silhouettes'); > 
>-	$text=WT_I18N::translate('Use silhouette images when no highlighted 
>image for that individual has been specified. The images used are 
>specific to the gender of the individual in 
>question.<br><br><table><tr><td wrap valign="middle">This image might 
>be used when the gender of the individual is unknown:') > 
>+	$text=WT_I18N::translate('Use silhouette images when no highlighted 
>image for that individual has been specified. The images used are 
>specific to the gender of the individual in 
>question.<br><br><table><tr><td style="vertical-align:middle">This 
>image might be used when the gender of the individual is unknown:')
>Changes to translatable text will cause all existing translations to be 
>lost.
>
>If you are just correcting the English text (e.g. spelling/puncutation) 
>and do not want the translated text to change, then you must also 
>update the corresponding msgid in each of the .PO files.
>
>If this is a change to the content/meaning of the English text (as in 
>this case), you must also update the corresponding msgstr in the .PO 
>files.
>
>(NOTE: Having markup in the translation strings like this is bad 
>practice - for this reason. But this text was probably inherited from 
>PGV.)
>
>(NOTE2: This only applies to .PO files that contain a translation. If 
>the text is untranslated for any particular language, then it is not 
>necessary to make this update, as there is no translation to be 
>lost...)
>
>—
>Reply to this email directly or view it on GitHub.
>