branch to github.
Greetings,
wintertime
Gesendet: Freitag, 03. April 2020 um 10:22 Uhr
Von: "D Blakeley via Freecol-developers"
An: "Michael T. Pope" , "David Lewis"
Cc: "FreeCol Developers" , "freecol-website-requ...@lists.sourceforge.net
1. I'm guessing the issue David is talking about below is why there hasn't
been a release since Feb? FYI Marcin is asking again for a new release to test
Mikes latest changes presumably.
2. Mike I've followed your instructions (thanks again) and fixed all the map
names (shorter and no spaces)
Hi Mike,
I haven't had a chance to look to determine why yet, but the master branch
CI builds are failing.
This could have been due to a bad change that I merged in last week or so.
If you have a chance to take a look at it, that'd be great. Otherwise, I'll
try and get to that later this week.
Br
On Sun, 15 Mar 2020 11:47:42 + (UTC)
D Blakeley wrote:
> I've gotta say with all due respect it seems strange that the whole map usage
> system requires manual entry into some translation list instead of storing
> the required extra info in the map files themselves and simply having a map
>
Hi Mike,
Right! This I can follow lol! Thank you yes I can proceed further now lol.
When you originally talked about "FreeColMessages.properties" I thought you
were talking about some line value within some master translation file that I
had no idea where to find lol. But now I see you meant
F
> Just letting you know the good news that a number of different people are
> making contributions to FreeCol on github...
Quite so. Pity they are a bit down the list. I was away last week, and
am now stuck at github issue#32 which is proving to be a PITA, and there is
a new sourceforge bug to
Hi guys,
Just letting you know the good news that a number of different people are
making contributions to FreeCol on github. There are a whole bunch of new pull
requests there. Mine PR has been sitting there for weeks too (with a mystery
problem no one has helped on) but it would suck even more