*addon - weather.metoffice
*version - 1.0.2
*url - git://github.com/powlo/weather.metoffice.git
*revision - 6c2bf56e70ecfee362a83dfd735d7f902d5105cf
*branch - master
*xbmc version - jarvis, isengard
--
Transform
added to helix
regards,
Martijn Kaijser
XBMC Foundation
On 1 March 2015 at 20:17, Paul Backhouse paul_backho...@hotmail.com wrote:
*addon - weather.metoffice
*version - 1.0.1
*url - https://github.com/powlo/weather.metoffice.git
*tag - v1.0.1
*branch - master
*xbmc version - helix
added to repo
regards,
Martijn Kaijser
Team XBMC
On Tue, Apr 8, 2014 at 4:34 PM, Paul Backhouse
paul_backho...@hotmail.comwrote:
Translation capability added.
*revision - 9c5ee677ce
--
Put Bad Developers to
Yep, that's pretty much what I've started doing. It's sub-optimal in
that it requires two tables to be maintained where there should only be
one, but its the best solution given the constraints.
--
Put Bad Developers to
Translation capability added.
*revision - 9c5ee677ce
--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test Deployment
Start a new project now. Try
ok some issues found
icon.png needs to be 256x256
any text used as label needs to be added to strings.po so it can be
translated.
See
http://wiki.xbmc.org/index.php?title=Add-on_structure#resources.2Flanguage.2F
and
On 07/04/14 11:51, Martijn Kaijser wrote:
any text used as label needs to be added to strings.po so it can be
translated.
Hmm. I really dislike XBMC's translation mechanism. It makes code less
readable, not more.
Is it acceptable to use python's builtin translation tools?
which tools?
this is how the system works and is mandatory for every addon in our repo.
regards,
Martijn Kaijser
Team XBMC
On Mon, Apr 7, 2014 at 2:41 PM, Paul Backhouse
paul_backho...@hotmail.comwrote:
On 07/04/14 11:51, Martijn Kaijser wrote:
any text used as label needs to be added to
On 07/04/14 13:45, Martijn Kaijser wrote:
which tools?
https://docs.python.org/2/library/gettext.html
--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate
That makes no difference at all as this will not work for the Settings.xml
so you will still need to use the strings.po for starters.
Also I see no advantages using the Python tools with taking into account
you still need to get the set xbmc gui language which the build in method
auto handles.
On
On 07/04/14 17:48, Martijn Kaijser wrote:
That makes no difference at all as this will not work for the
Settings.xml so you will still need to use the strings.po for starters.
Ah OK I didn't realise you wanted xml strings translated too. But it
makes sense.
Also I see no advantages using
Hi,
have a look how I do the translation in my add-ons:
- Define a string dict:
https://github.com/dersphere/plugin.video.hdtrailers_net/blob/master/addon.py#L23(This
can also be a seperate file)
- Create a small helper function:
On 04/04/14 22:24, Martijn Kaijser wrote:
incomplete PR.
need more info as stated on the wiki.
My apologies.
*addon - weather.metoffice
*version - 1.0.0
*url - git://github.com/powlo/weather.metoffice.git
*revision - af52bf5d55827d30480db3e4612579ca3cdd577c
*branch - master
*xbmc
url: https://github.com/powlo/weather.metoffice
Branch: master
--
___
Xbmc-addons mailing list
Xbmc-addons@lists.sourceforge.net
incomplete PR.
need more info as stated on the wiki.
and from quick look your dependencies don't match in addon.xml
regards,
Martijn Kaijser
Team XBMC
On Fri, Apr 4, 2014 at 11:06 PM, Paul Backhouse
paul_backho...@hotmail.comwrote:
url: https://github.com/powlo/weather.metoffice
Branch:
15 matches
Mail list logo
