[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-l10n] AoPeM strange text

Hi Donald,
Le 16/06/2020 à 00:38, Donald a écrit :
> In Weblate
> Source string comment AoPeM
> There appears to be something wrong with this text. It ends with "or",
> which is unlikely to be correct.
> Is the programmer trying to put together sentences from more than one
> element? I think that is to be avoided, as the resulting word order may
> be wrong.
> Click the <emph>Create Query in SQL View</emph> icon <image
> id="img_id3154071" src="cmd/sc_dbnewquerysql.png" width="0.1862in"
> height="0.1862in"><alt id="alt_id3154071">Icon</alt></image> or

Could you send the link (icon at the top right in front of Translation)
to the string, I'd like to have a look to the nearby strings. Thanks,
Sophie Gautier sophi@libreoffice.org
GSM: +33683901545
IRC: sophi
Foundation coordinator
The Document Foundation

To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-l10n] AoPeM strange textDonald <odze5261@libreoffice.org>
[libreoffice-l10n] Website stringssophi <sophi@libreoffice.org>
[libreoffice-l10n] AoPeM strange textDonald <donr2648@fastmail.fm>
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.