Times are UTC Toggle Colours
07:06:24 *** oskari89 has joined #openttdcoop.devzone 07:10:57 *** oskari892 has joined #openttdcoop.devzone 07:11:12 *** oskari892 has quit IRC 07:45:51 *** Supercheese has quit IRC 07:59:26 *** Taede has quit IRC 08:03:00 *** TWerkhoven has joined #openttdcoop.devzone 08:20:09 *** TWerkhoven has quit IRC 08:23:42 *** TWerkhoven has joined #openttdcoop.devzone 10:07:57 <DevZone> Project Finnish Rail Infrastructure - Rails build #54-push: SUCCESS in 58 sec: https://jenkins.openttdcoop.org/job/frissrails/54/ 10:52:51 <DevZone> Project Finnish Rail Infrastructure - Rails build #55-push: FAILURE in 26 sec: https://jenkins.openttdcoop.org/job/frissrails/55/ 10:53:28 <oskari89> Where you can see the reason for failure? 10:54:05 <phatmatt> https://jenkins.openttdcoop.org/job/frissrails/55/console 10:54:13 <phatmatt> 10:52:51 nmlc ERROR: Image file "gfx/signals/semaphores.png": Palette is not recognized as a valid palette. 10:54:31 <oskari89> Hmm O_o 10:55:04 <oskari89> Let's see if it fixes... 10:56:15 <oskari89> Where were palettes on devzone 10:56:42 <V453000> helpcenter 10:56:44 <oskari89> I used photoshop-dos-noact-no1cc 10:56:49 <V453000> there are documents I think 10:57:50 <V453000> you dont usecompany colours? O_O 10:58:13 <oskari89> No i don't 10:58:15 <oskari89> On those signals 10:59:13 <oskari89> http://dev.openttdcoop.org/documents/1 10:59:58 <V453000> well idk, I use photoshop-ttd-dos.act - Photoshop palette DOS (768 Bytes) Delete 11:00:08 <V453000> and it works just fine 11:00:22 <oskari89> Let's see.. 11:05:40 <oskari89> ... if it's still failure 11:05:51 <DevZone> Yippie, build fixed! 11:05:52 <DevZone> Project Finnish Rail Infrastructure - Rails build #56-push: FIXED in 37 sec: https://jenkins.openttdcoop.org/job/frissrails/56/ 11:05:55 <oskari89> :DDDD 11:05:59 <oskari89> Yeah :) 11:06:17 <phatmatt> you are the master debugger 11:06:49 <oskari89> Just used the palette V453000 mentioned :) 11:16:21 *** Zuu has joined #openttdcoop.devzone 11:18:08 <planetmaker> oskari89, you cannot save a file with a palette like noact-no1cc 11:18:31 <planetmaker> you can only convert an image to that palette to make sure it has no action and CC colours. then you need to convert it back to the usual palette 11:19:17 <planetmaker> what V linked is the full palette :-) Thus using that you did just that 11:38:44 <V453000> :d 11:38:48 <V453000> :) 12:04:27 <oskari89> :D 12:14:44 <V453000> oskari89: are you converting it to indexed image - select palette, or just opening it as swatches? :) is a difference 12:39:38 <oskari89> Converting to indexed image 12:42:25 <V453000> idk how could that possibly break :) 12:42:45 <oskari89> By selecting the noact-no1cc 12:42:46 <oskari89> :P 12:42:49 <oskari89> And saving 12:42:56 <V453000> the one I linked to works? 12:43:02 <oskari89> Lesson learned, yeah :) 12:43:06 <V453000> oh, good :) 12:43:48 <V453000> it is kinda advantage too for things which dont change CC like rails/signals as you can freely use the blue/green colour without having them recolour :) 12:46:36 <V453000> esp green is a kind of pain to set up nicely for things like vehicles if you dont want to use recolour sprites 12:46:39 <V453000> blue is k 12:48:20 <planetmaker> V453000, there's a slight danger it doing so: the sprites could suddenly gain the capability to support CC ;-) 12:49:17 <planetmaker> http://hg.openttd.org/openttd/trunk.hg/rev/1c5beb280282 12:49:25 <planetmaker> http://hg.openttd.org/openttd/trunk.hg/rev/6cd61e4c61a9 12:50:38 <V453000> LOL 12:50:59 <V453000> well whatever :) can fix anytime when it breaks 12:51:04 <planetmaker> also r20379, r12447 12:51:16 <planetmaker> :-) yup! :-) 13:03:19 <oskari89> Hmm, what kind of photos one could do with ttd-dos palette... ;) 13:03:34 <oskari89> Let's see 13:03:46 <oskari89> I think it would turn art that way :P 13:05:21 <oskari89> Actually, not bad result 13:05:49 <planetmaker> 198 colours are quite a few :-) 13:06:06 <planetmaker> could you name them all? ;-) 13:06:13 <oskari89> :D 13:06:25 <oskari89> It gives a "film" look 13:06:35 <oskari89> Could try layering 13:06:53 <planetmaker> :-) remembers me of some graphics from ancient adventure games like space quest 13:07:47 <oskari89> :D 13:07:54 <oskari89> Try yourself 13:08:09 <planetmaker> I know, yes 13:08:12 <oskari89> It's a little game-look 13:19:38 <V453000> LOL I never tried that actually 13:43:32 <oskari89> V453000: Try ;) 13:44:00 <V453000> at werk now :) 13:44:15 <V453000> and at home I will probably be interested in making actual sprites :P 14:01:32 <oskari89> Can i define multiple URL's with STR_GRF_URL ? 14:02:23 <V453000> provide links from the one url instead? :D 14:14:01 <planetmaker> you can provide as many as you want. But if it's not a valid link, it simply won't open. Two links concatenated aren't valid either :-) 14:18:52 <oskari89> Okay :P 14:19:14 <oskari89> I love Notepad++ 14:19:27 <oskari89> It is so versatile when editing lng and nml files 14:24:48 <V453000> ze chameleon is nice indeed :) 14:53:53 <TWerkhoven> ello 15:01:13 <planetmaker> oskari89, just to be clear: no, only one URL makes sense. Or you will have a non-working URL button 15:01:58 <planetmaker> oskari89, and you use http://dev.openttdcoop.org/projects/nml/repository/changes/contrib/create_notepadpp_highlighter ? 15:04:17 *** ODM has joined #openttdcoop.devzone 15:31:00 *** TWerkhoven is now known as Taede 15:47:09 <oskari89> pm: I think i do :) 16:01:59 *** Zuu has quit IRC 16:02:24 *** Zuu has joined #openttdcoop.devzone 16:15:06 <DevZone> Project Finnish Rail Infrastructure - Rails build #57-push: SUCCESS in 48 sec: https://jenkins.openttdcoop.org/job/frissrails/57/ 16:15:46 <DevZone> Project Finnish Rail Infrastructure build #34-push: SUCCESS in 37 sec: https://jenkins.openttdcoop.org/job/friss/34/ 16:23:18 <DevZone> Project Finnish Rail Infrastructure - Rails build #58-push: SUCCESS in 50 sec: https://jenkins.openttdcoop.org/job/frissrails/58/ 16:53:04 *** Alberth has joined #openttdcoop.devzone 16:55:03 <DevZone> Project OpenGFX build #30-push: SUCCESS in 7 min 26 sec: https://jenkins.openttdcoop.org/job/opengfx/30/ 16:55:59 <DevZone> Project OpenGFX+ Airports build #13-push: SUCCESS in 55 sec: https://jenkins.openttdcoop.org/job/airportsplus/13/ 17:02:25 <DevZone> Project FIRS Industry Replacement Set build #19-push: SUCCESS in 6 min 26 sec: https://jenkins.openttdcoop.org/job/firs/19/ 17:03:08 <DevZone> Project ISR Industrial Station Renewal build #21-push: SUCCESS in 43 sec: https://jenkins.openttdcoop.org/job/isr/21/ 17:04:01 <DevZone> Project OpenMSX build #9-push: SUCCESS in 52 sec: https://jenkins.openttdcoop.org/job/openmsx/9/ 17:06:26 *** frosch123 has joined #openttdcoop.devzone 17:06:47 <planetmaker> <3 eints :-) 17:13:53 <DevZone> Project OpenGFX+ Landscape build #8-push: SUCCESS in 26 min: https://jenkins.openttdcoop.org/job/ogfx-landscape/8/ 17:16:00 <oskari89> 26 minutes :D 17:18:21 <DevZone> Project NML - NewGRF Meta Language build #58-nightlies: SUCCESS in 1 min 7 sec: https://jenkins.openttdcoop.org/job/nml/58/ 17:18:57 <planetmaker> yes... 26 minutes 17:19:16 <planetmaker> (nearly) all sprites generated from gimp sources when building it :-) 17:19:20 <oskari89> How large is the source :D 17:19:49 <DevZone> Project Finnish Trainset build #38-push: SUCCESS in 2 min 21 sec: https://jenkins.openttdcoop.org/job/finnishtrainset/38/ 17:20:26 <Alberth> not so large, it generates everything :) 17:20:49 <Alberth> zBase is a lot worse :) 17:20:49 <frosch123> moin :) 17:21:01 <planetmaker> source images are like 6MByte 17:21:14 <planetmaker> but the layers are composed differently for different sprites 17:21:21 <planetmaker> Thus much less drawing for many many ground sprites :-) 17:21:31 <oskari89> zBase 10 min :P 17:21:33 <planetmaker> and it makes sure that the ground sprites match properly 17:21:42 <planetmaker> yes. zBase doesn't generate sprites 17:22:11 <planetmaker> ogfx+landscape invokes gimp and exports each spriteset from the gimp files 17:22:16 <planetmaker> into separate files 17:22:19 <planetmaker> that takes a bit time 17:22:38 <oskari89> Yeah 17:24:11 <Alberth> make -j :p 17:24:49 <planetmaker> yes... I chose to not enable that on the CF. So that other projects can still build in parallel 17:25:08 <planetmaker> locally I always build it with like -j6 ... -j8 17:25:20 <planetmaker> speeds up things nicely :D 17:27:44 <Alberth> :) 17:31:17 *** gelignite has joined #openttdcoop.devzone 17:57:13 <DevZone> Project Finnish Trainset build #39-push: SUCCESS in 2 min 19 sec: https://jenkins.openttdcoop.org/job/finnishtrainset/39/ 18:19:32 *** andythenorth has joined #openttdcoop.devzone 18:20:08 <Alberth> o/ 18:21:44 <andythenorth> o/ 18:21:55 <planetmaker> o/ 18:22:20 <oskari89> planetmaker, could we get those old revision systems back on the two FRISS projects? 18:22:33 <oskari89> Like the Finnish Trainset has r307 or so 18:22:52 <DevZone> Project eints build #5-nightlies: SUCCESS in 13 sec: https://jenkins.openttdcoop.org/job/eints/5/ 18:22:53 <DevZone> Alberth <alberth@openttd.org>: Fix: Consider unknown string parameters to be critical in getting the count exactly matching. 18:23:06 <planetmaker> why? 18:23:32 <oskari89> FRISS rail infrastructure version [date] [5011:md5] is much longer than simply just rxxx 18:23:40 <planetmaker> feel free to change the grf-internal revisioning system, if you like 18:23:45 <planetmaker> rXXX is simply not unique 18:24:03 <oskari89> Can it be changed from makefile? 18:24:13 <planetmaker> your rXX might be my rYY and vice versa 18:24:34 <planetmaker> and there's nothing I can do about. Or rather: what I could do about is what I did implement. That's the 5011 18:24:46 <planetmaker> though that's not entirely unique, too. Unique is the md5 18:24:52 <planetmaker> and only that 18:25:30 <planetmaker> and as the md5 is not nicely readable, I amend it by date and a numeric version. thus [date] [rrrr:md5] 18:25:40 <Alberth> unknown string parameters are specially added by the author, so they look special enough to me to warrant that they are also in a translation 18:25:53 <planetmaker> with the added bonus that you know ingame always from when the newgrf originates 18:26:07 <DevZone> Project Finnish Rail Infrastructure - Rails build #59-nightlies: SUCCESS in 53 sec: https://jenkins.openttdcoop.org/job/frissrails/59/ 18:26:25 <planetmaker> Alberth, yes. But it looks out of context. You meant to say that elsewhere? :-) 18:26:42 <planetmaker> (I agree with that assessment) 18:27:23 <planetmaker> oskari89, yes, you can change what is displayed to the user. You can also change that in Makefile.config 18:27:36 <planetmaker> Add a line like 18:27:57 <Alberth> I didn't say that, devzone did, I pushed a commit like that to eints yesterday evening 18:28:17 <planetmaker> REPO_VERSION_STRING ?= $(shell [ -n "$(REPO_TAGS)" ] && echo $(REPO_TAGS)$(REPO_MODIFIED) || echo $(REPO_DATE)$(REPO_BRANCH_STRING) \($(NEWGRF_VERSION):$(REPO_HASH)$(REPO_MODIFIED)\)) 18:28:31 <planetmaker> and compose your REPO_VERSION_STRING however you like :-) 18:29:08 <Alberth> ie revision 310 of eints 18:29:12 <planetmaker> replace the ?= by a simple = in that line, if you add it to Makefile.config 18:29:29 <DevZone> Project Nutracks build #16-nightlies: SUCCESS in 16 sec: https://jenkins.openttdcoop.org/job/nutracks/16/ 18:29:51 <planetmaker> yup, I saw that. It seemed to have barfed on my strings for the base sets (where I added the version string as IRC Log Viewer to the strings) 18:30:18 <planetmaker> custom tags are allowed in NML by means of custom_tags.txt. So yes, it's good to not translate them and require them to be present in each 18:31:04 <planetmaker> ^ @ Alberth 18:31:19 <planetmaker> (just to be clear... two conversations at the same time can be confusing :D ) 18:32:11 <Alberth> I am truly lost what your "why?" was about now :) 18:32:43 <Alberth> was it about devzone spitting out my commit messages, or were you asking about why of that commit? 18:32:47 <Alberth> the latter not apparently 18:32:56 <planetmaker> sorry, my why was directed at oscar :-) 18:33:21 <Alberth> lol :) 18:33:44 <planetmaker> :-) 18:33:57 <Alberth> ok, why does devzone highlight me? 18:34:04 <planetmaker> honestly... no clue :S 18:34:26 <planetmaker> actually... yes... probably slightly mis-configured IRC module for eints project 18:34:32 <Alberth> ok 18:34:37 <planetmaker> by default it tells about changes in the built, too 18:34:44 <planetmaker> and... ^ I didn't change that obviously 18:34:48 <Alberth> nicely on time then :p 18:35:08 <planetmaker> well, eints neightly doc update was built :-) 18:35:16 <planetmaker> so it told us :-) 18:35:27 <Alberth> you disabled that? 18:35:40 <Alberth> apparently not or not enough thus :) 18:36:00 <planetmaker> not yet. Just doing now. Disabling the IRC announcement of changes 18:36:30 <planetmaker> yeah, was summary + scm changes 18:37:40 <planetmaker> thus in the future you'll not get highlights from eints project anymore when it is built :-) 18:37:59 <Alberth> :) 18:38:04 <Alberth> thanks 18:38:19 <planetmaker> yeah, should be default. Was just an oversight when configuring 18:38:54 <planetmaker> for custom project configs I might sometimes miss one thing or another :-) 18:39:50 <DevZone> Project Finnish Rail Infrastructure - Rails build #60-push: SUCCESS in 31 sec: https://jenkins.openttdcoop.org/job/frissrails/60/ 18:40:28 <planetmaker> oskari89, anyway, I'd quite strongly recommend to keep the 'days since 1.1.2000' as version at least. If you want it shorter displayed ingame, use a string like 18:40:43 <DevZone> Project OpenGFX+ Industries build #22-nightlies: SUCCESS in 27 sec: https://jenkins.openttdcoop.org/job/ogfx-industries/22/ 18:41:06 <planetmaker> REPO_VERSION_STRING ?= $(shell [ -n "$(REPO_TAGS)" ] && echo $(REPO_TAGS)$(REPO_MODIFIED) || echo $(NEWGRF_VERSION)$(REPO_MODIFIED)) 18:41:17 <planetmaker> REPO_VERSION_STRING = $(shell [ -n "$(REPO_TAGS)" ] && echo $(REPO_TAGS)$(REPO_MODIFIED) || echo $(NEWGRF_VERSION)$(REPO_MODIFIED)) 18:41:26 <planetmaker> ^ the last one. Add it to your Makefile.config 18:42:00 <oskari89> That gives the revision on repo on grf list? 18:42:12 <planetmaker> that gives today 5010 18:42:21 <planetmaker> or rather for commits from today 18:43:13 <planetmaker> but! if you compare different versions from today you'll have a very hard time to figure out which. 18:43:21 <DevZone> Project Finnish Rail Infrastructure build #35-push: SUCCESS in 48 sec: https://jenkins.openttdcoop.org/job/friss/35/ 18:43:24 <oskari89> I'd still like to have the r[repo revison] on the grf-list :) 18:43:29 <planetmaker> And that's why I explicitly DO NOT recommend to change it to that 18:44:10 <planetmaker> oskari89, yes. But the revision can change. This is not SVN. Your r307 will build here as r322. And maybe on the DevZone as r302 18:44:16 <planetmaker> do you really want that? 18:44:39 <planetmaker> the revision as we used before, it's actually based on many fragile assumptions 18:44:46 <planetmaker> and I've seen them breaking 18:44:55 <oskari89> Okay 18:45:25 <planetmaker> that's why I made this change really. To be a bit saver that the reported version to OpenTTD is continuous. 18:45:38 <oskari89> And on releases, does it just change to [grf name] 0.x.x? 18:45:45 <planetmaker> And that we ingame see easier what what version we deal with (thus date + newgrf version + hash) 18:45:51 <planetmaker> yes 18:46:00 <oskari89> (The name visible to grf list) 18:46:02 <planetmaker> release display is unchanged 18:46:47 <oskari89> Ok 18:46:52 <planetmaker> but as said: you can in principle change the display thing to anything you like... it's just what the user sees ingame 18:46:53 <DevZone> Project Iron Horse build #173-nightlies: SUCCESS in 38 sec: https://jenkins.openttdcoop.org/job/iron-horse/173/ 18:47:33 <planetmaker> as long as you only change the REPO_VERSION_STRING you only change what is shown to the user. The numerical version reported to openttd is not touched by that. So it's safe to play with the display version string 18:49:49 <planetmaker> oskari89, as example for when the rXXX fails: assume you commit something to the repo. And juzza does, too. At approx. the same time 18:50:00 <planetmaker> you both push. And then one of you merges the two changesets 18:50:48 <oskari89> Yes? 18:50:59 <planetmaker> in your repo you'll have like r310: "blablah" ( oskari89 ); r311: "blu bla" (juzza). While he'll have: r310: "blu bla" (juzza); r311: "bla bla" ( oskari89 ) 18:51:19 <planetmaker> and on the devzone you'll have who ever was faster 18:51:22 <planetmaker> to push 18:51:54 <oskari89> Yes 18:52:03 <planetmaker> all will have r312: "Merge" (whoever) 18:52:10 <planetmaker> possibly :-) 18:52:39 <Alberth> the problem is thus that r310 does not tell what I have exactly 18:53:01 <oskari89> Fortunately i only use Jenkins-build grf's now :P 18:53:10 <planetmaker> :D 18:53:14 <oskari89> In developing 18:53:23 <planetmaker> seems to become a common thing to do 18:53:43 <oskari89> Yeah, makes sense 18:54:00 <planetmaker> well... I still build first locally, see that it works and then push :-) 19:02:22 <DevZone> Project Finnish Trainset build #40-push: SUCCESS in 2 min 35 sec: https://jenkins.openttdcoop.org/job/finnishtrainset/40/ 19:03:34 <DevZone> Project OpenGFX build #31-nightlies: SUCCESS in 6 min 20 sec: https://jenkins.openttdcoop.org/job/opengfx/31/ 19:12:46 *** Supercheese has joined #openttdcoop.devzone 19:19:21 <oskari89> (perfecting language strings atm) :) 19:19:44 <DevZone> Project Finnish Rail Infrastructure - Rails build #61-push: SUCCESS in 40 sec: https://jenkins.openttdcoop.org/job/frissrails/61/ 19:34:48 <planetmaker> the english ones? :D 19:49:32 <Supercheese> that reminds me, I should fix the fake subways english strings to help translations 19:54:25 <planetmaker> :-) 19:56:52 <Supercheese> well, that one problematic string anyway 19:57:50 <DevZone> Project Fake Subways build #10-push: SUCCESS in 36 sec: https://jenkins.openttdcoop.org/job/fake-subways/10/ 19:59:10 <Supercheese> wonder how long it takes for changes to migrate to eints after a push 19:59:21 <Supercheese> at the nightly translation-commit time? 20:02:32 <planetmaker> every 5 minutes or so afaik 20:03:06 <Supercheese> I wonder how it'll handle my changing of the base language 20:03:15 <Supercheese> well, "language" 20:03:28 <planetmaker> it will pick them up. And translations will report as missing or outdated 20:03:44 <Supercheese> :) 20:04:39 *** Zuu has quit IRC 20:05:08 <DevZone> Project Iron Horse build #174-push: SUCCESS in 32 sec: https://jenkins.openttdcoop.org/job/iron-horse/174/ 20:07:38 <DevZone> Project Iron Horse build #175-push: SUCCESS in 33 sec: https://jenkins.openttdcoop.org/job/iron-horse/175/ 20:08:13 <Supercheese> EQVVS FERREVS 20:09:13 <Supercheese> Hey, there's no langid for Latin 20:09:20 <Supercheese> :( 20:09:20 <planetmaker> EQUUS FERRUS 20:09:25 <DevZone> Project Iron Horse build #176-push: SUCCESS in 44 sec: https://jenkins.openttdcoop.org/job/iron-horse/176/ 20:09:31 <planetmaker> without E ;-) 20:09:42 <Supercheese> I learned ferreus as the adjective form 20:09:46 <Supercheese> hmm 20:09:55 <planetmaker> hm, that's different, the adjective? then maybe :-) 20:09:59 <Supercheese> yeah, "made of iron" 20:10:19 <Supercheese> Equus ferrī might work with the genitive 20:10:28 <planetmaker> http://en.wiktionary.org/wiki/ferrum you might be right :-) 20:10:29 <Webster> Title: ferrum - Wiktionary (at en.wiktionary.org) 20:10:34 *** ODM has quit IRC 20:10:50 <Supercheese> http://en.wiktionary.org/wiki/ferreus#Latin 20:10:51 <Webster> Title: ferreus - Wiktionary (at en.wiktionary.org) 20:11:10 <Supercheese> eints doesn't support Latin anyway 20:11:19 <Supercheese> nor OTTD, it seems 20:11:19 <planetmaker> not? 20:11:27 <DevZone> Project Iron Horse build #177-push: SUCCESS in 36 sec: https://jenkins.openttdcoop.org/job/iron-horse/177/ 20:11:30 <planetmaker> Supercheese, make a latin translation and it can :-) 20:11:39 <Supercheese> That's... a lot of strings 20:11:44 <planetmaker> usual rules: translate ~<90% and we add it 20:11:49 <Supercheese> whew 20:11:55 <Supercheese> well, certainly possible 20:11:57 <planetmaker> yes, that's 4000 strings plust a few :-) 20:12:04 <planetmaker> but many are 'boring' strings, too 20:12:05 <Supercheese> lots of terminology that didn't exist in the Roman era, of course 20:12:21 <Supercheese> it'd end up neo-Latin 20:12:26 <planetmaker> we once had a 'pig latin' translation, I think 20:12:30 <Supercheese> :D 20:16:48 <DevZone> Project Iron Horse build #178-push: SUCCESS in 57 sec: https://jenkins.openttdcoop.org/job/iron-horse/178/ 20:17:33 <planetmaker> A latin translation IMHO might be nice. But yes, would need one (or a few) to maintain it :-) 20:19:47 <DevZone> Project Iron Horse build #179-push: SUCCESS in 36 sec: https://jenkins.openttdcoop.org/job/iron-horse/179/ 20:21:00 <DevZone> Project Iron Horse build #180-push: SUCCESS in 35 sec: https://jenkins.openttdcoop.org/job/iron-horse/180/ 20:22:57 <DevZone> Project Iron Horse build #181-push: SUCCESS in 33 sec: https://jenkins.openttdcoop.org/job/iron-horse/181/ 20:26:40 <DevZone> Project Iron Horse build #182-push: SUCCESS in 45 sec: https://jenkins.openttdcoop.org/job/iron-horse/182/ 20:26:53 <Alberth> you always hope that andy stops adding stuff before the execution time grows beyond the comfort zone :) 20:27:28 <planetmaker> :-) 20:28:29 <andythenorth> brot can't keep up :P 20:28:34 <andythenorth> my tickets aren't getting closed 20:29:19 <planetmaker> brot has nothing to do with issues being closed or not. It's just a stupid bot which queries what is being done. And being slow about that 20:29:41 <DevZone> Project Iron Horse build #183-push: SUCCESS in 35 sec: https://jenkins.openttdcoop.org/job/iron-horse/183/ 20:30:38 <planetmaker> Supercheese, but changing base language on the fly... not sure whether that worked :-) 20:31:06 <frosch123> i am not sure whether eints allows changing base language 20:31:18 <planetmaker> we now have a test case :-) 20:31:21 <DevZone> Project Iron Horse build #184-push: SUCCESS in 34 sec: https://jenkins.openttdcoop.org/job/iron-horse/184/ 20:31:21 <planetmaker> fakesubways did 20:31:28 <frosch123> from what to what? 20:31:37 <planetmaker> en_GB -> en_US 20:31:46 <planetmaker> 0x01 -> 0x00 20:33:42 <planetmaker> Supercheese, and I was not aware that you meant *changing* the base language as in switching to another language :-) 20:34:35 <planetmaker> what I really like about web translator is that I can even help by translating one single string :-) 20:34:47 <planetmaker> for me it really lowers the barrier to translate something 20:35:47 <frosch123> well, uploading did not fail, but it did not affect eints either 20:36:49 * andythenorth wonders about making more grfs translatable :P 20:36:54 <planetmaker> :-) 20:37:09 <andythenorth> not really sure what is needed 20:37:23 <Alberth> I would really be surprised if you could change the base language :) 20:37:24 <planetmaker> needed are *.lng files 20:37:40 * andythenorth experiments 20:37:47 <andythenorth> this is going to be truly horrible though :P 20:37:47 <frosch123> Alberth: it did not work, but it did not fail either 20:38:06 <planetmaker> andythenorth, what you basically need to do is: rename *.lang.in into *.lng 20:38:07 <frosch123> the data file still says baselang="en_GB" 20:38:16 <Alberth> interesting 20:38:19 <planetmaker> and either a) generate the lang files into a new directory 20:38:24 <frosch123> but i have no idea what the commit scripts says 20:38:33 <frosch123> it did not coplain on upload-baselang upload-translations 20:38:36 <planetmaker> or b) move the then re-named lang files into a new directory and generate the lang files into the current one 20:38:45 <frosch123> but i am worried it will fail on download-translations 20:38:51 <andythenorth> afaict, I have to have the compile duplicate to english.lng.bak, append to english.lng, then swap them back when compile finishes 20:38:53 <Alberth> I would guess that it does fail, but the sync script hides the error or so 20:38:54 <frosch123> by downloading us instead of gb or so 20:39:15 <andythenorth> having two english.lng files is out of the question? 20:39:24 <Alberth> it queries the base language from eints afaik 20:39:26 <andythenorth> inventing my own lang for the grf is out of the question? 20:39:27 <planetmaker> would be confusing, no? 20:39:41 <planetmaker> well, having them in different dirs is no problem. If one is auto-generated 20:39:47 <andythenorth> can nml use both? 20:39:52 <planetmaker> no 20:39:54 <Alberth> andythenorth: your own lang? 20:39:59 <andythenorth> iron_horse.lng :P 20:40:05 <andythenorth> fish.lng :P 20:40:12 <planetmaker> it's not about filenames 20:40:12 <Taede> why make up your own when theres fantasy ones about already 20:40:16 <andythenorth> some people have klingon 20:40:16 <Taede> elvish, klingon 20:40:17 <planetmaker> just about file extension, andy 20:40:19 <andythenorth> and bork-bork 20:40:58 <andythenorth> planetmaker: ? 20:41:25 <planetmaker> andythenorth, what would be easiest: rename the current lang dir into lang-in dir 20:41:34 <planetmaker> rename all lang.in files into lng files 20:41:54 <planetmaker> adopt your generation script to include the lang-in/*.lng files and put generated output into lang dir 20:41:58 <Alberth> andythenorth: as long as the langgrfids match, I don't care about file names 20:42:45 <frosch123> so, what to do? 20:42:51 <frosch123> delete the project from eints? 20:43:05 <frosch123> trash pm changes while doing so? :p or commit first? :p 20:43:15 <planetmaker> trash that, no problem 20:43:20 <Alberth> would be the simplest solution imho 20:43:40 <frosch123> but i wonder why "Error: grf language ids of the base language do not match, --base-lang claims {} while remote claims {}" is not triggered 20:44:12 <frosch123> i guess i want to know that first :) 20:45:03 <andythenorth> hmm 20:45:08 * andythenorth needs some python file handling code :P 20:45:48 <andythenorth> shutil is my friend :P 20:49:35 <V453000> dying 20:49:44 <planetmaker> ? 20:50:47 <andythenorth> fuck 20:51:00 <andythenorth> I have to switch the files back when the compile finishes :( 20:51:09 <andythenorth> that has to be done after nml has finished :( 20:51:14 <planetmaker> eh? 20:51:17 <andythenorth> dunno how to do that :( 20:51:36 <planetmaker> that's why I say: use two different dirs 20:51:46 <planetmaker> one with the lng files like now 20:51:55 <planetmaker> and one where you output the stuff of your generation script 20:52:11 <andythenorth> I couldn't follow that solution :) 20:52:32 <andythenorth> I don't understand how it concatenates to english.lng 20:52:57 <andythenorth> I understood the rest of it 20:53:21 <planetmaker> well... how... possibly copy the english.lng. And open rw with appending your stuff 20:53:38 <andythenorth> let me see if I understood 20:54:13 <andythenorth> eints wants to read from 'lang', yes/no? 20:54:30 <planetmaker> default: yes. Needed: no 20:54:37 <planetmaker> better: no 20:54:41 <andythenorth> and nmlc can get lang from anywhere via param 20:54:42 <planetmaker> (easier for compilation) 20:54:56 <planetmaker> yes. either or needs changing. better change default eints dir imho 20:55:02 <andythenorth> hmm, maybe I have understood your solution, but backwards :) 20:55:28 <andythenorth> ok, so copy whole lang dir during compile, concatenate to file(s), rm dir at end of compile 20:55:33 <andythenorth> will work 20:55:39 <planetmaker> why rm dir? 20:55:40 <planetmaker> no 20:55:48 <planetmaker> don't rm it. That's what clean is for 20:56:01 <andythenorth> fair point 20:56:52 <andythenorth> so for the tools, should I copy from 'lang' to 'lang_compiled', xor copy from 'lang_src' to 'lang' ? 20:57:22 <planetmaker> copy from lang_src to lang 20:57:31 <planetmaker> and we tell eints to translate in lang_src 20:57:36 <andythenorth> ok 20:58:05 <andythenorth> and I move a bit of template code out of their completely 20:58:10 <andythenorth> then everything is clean 20:58:15 <andythenorth> their / there /s 21:05:26 *** Alberth has left #openttdcoop.devzone 21:19:05 <andythenorth> incoming :P 21:20:09 <DevZone> Project FISH is ships build #12-push: FAILURE in 40 sec: https://jenkins.openttdcoop.org/job/fish/12/ 21:20:35 <planetmaker> let's see :-) 21:21:01 <andythenorth> intriguing :P 21:21:07 <planetmaker> he... dir doesn't exist? 21:21:13 <andythenorth> it's not in my hgignore 21:21:30 <planetmaker> did you hg mv lang lang_src? 21:22:41 <andythenorth> seems I rm-ed it? 21:22:56 <planetmaker> I have no lang files in my checkout anywhere, yes 21:22:57 * andythenorth reads the diff 21:23:03 <andythenorth> https://dev.openttdcoop.org/projects/fish/repository/revisions/a15d2e2b9071 21:23:05 <andythenorth> it's missing 21:23:14 <andythenorth> hmm 21:23:18 <andythenorth> hg is blind to that dir 21:23:30 <planetmaker> the files were removed from that dir 21:23:34 <planetmaker> shall I try fix? 21:24:00 <andythenorth> I am curious 21:24:03 <andythenorth> the dir is here locally 21:24:08 <andythenorth> but hg ignores it 21:24:15 <planetmaker> but the diff says you deleted all files in it 21:24:19 <planetmaker> see the link you posted 21:24:19 <andythenorth> yes 21:24:24 <andythenorth> that is the puzzle ;) 21:26:16 <andythenorth> ah 21:26:20 <andythenorth> hg never sees dirs 21:26:25 <andythenorth> and I have *.lng ignored 21:26:28 <planetmaker> nope it doesn't 21:26:40 <planetmaker> nmlc ERROR: "lang/english.lng", line 3: Undefined command "repo_vars" 21:26:40 <planetmaker> hmm 21:27:34 <planetmaker> an... english.lng contains the <!-- lines 21:28:01 <andythenorth> incoming (2) 21:28:03 <andythenorth> let's see 21:28:55 <planetmaker> shall I push my re-addition of lang files? 21:29:09 <andythenorth> no no 21:29:10 <andythenorth> :) 21:29:14 <planetmaker> k :-) 21:29:37 <andythenorth> jenkins is building 21:29:45 <DevZone> Yippie, build fixed! 21:29:45 <DevZone> Project FISH is ships build #13-push: FIXED in 1 min 20 sec: https://jenkins.openttdcoop.org/job/fish/13/ 21:30:06 <planetmaker> :-) 21:30:22 <andythenorth> there we go http://bundles.openttdcoop.org/fish/push/v5011-13/lang/ 21:30:35 <planetmaker> yippie! 21:30:35 <andythenorth> that is the dir used by nml 21:30:44 <andythenorth> so eints needs to use lang_src 21:31:06 <planetmaker> you want to add it? Shall I? 21:33:19 <andythenorth> please 21:34:52 <planetmaker> done 21:35:29 <planetmaker> so... maybe wait 5 minutes... I hope we'll find it then at https://translator.openttdcoop.org/projects 21:35:37 <DevZone> Project FISH is ships build #14-push: SUCCESS in 1 min 16 sec: https://jenkins.openttdcoop.org/job/fish/14/ 21:36:36 <andythenorth> do I need to upload base lang, or will it get it from repo? 21:36:46 <planetmaker> uh 21:36:58 <planetmaker> it should have gotten it... something went wrong 21:38:59 <Supercheese> Hm, eints didn't mark translations as outdated 21:39:48 <Supercheese> and as was mentioned, the base language change didn't carry over to eints 21:40:00 <planetmaker> hm... fish import... https://paste.openttdcoop.org/show/2647/ 21:40:39 <Supercheese> I was hoping to allow folks to change the en_GB strings, as I know "Subway" is more of a pedestrian under-crossing than the underground trains in British parlance 21:41:19 <planetmaker> I put a landir file in .devzone/translations/langdir with the appropriate relative path... I think hm 21:41:21 *** gelignite has quit IRC 21:41:40 <planetmaker> Supercheese, yes... but changing base lang... did not exactly work, I guess 21:41:45 <Supercheese> indeed it did not 21:41:54 <planetmaker> that was not a feature forseen :-) 21:42:01 <Supercheese> well, I messed it up at first upload 21:42:06 <Supercheese> I should have had en_US as base 21:42:14 <planetmaker> that people change mid-way their mind about what language rules the world^WNewGRF 21:42:20 <Supercheese> hehe 21:43:15 <Supercheese> my first experiment with the devzone, I was bound to make a mistake or three (or ten) 21:43:30 <planetmaker> well. No-one tested that really :-) 21:43:37 <andythenorth> planetmaker: lang_dir looks correct 21:43:42 <andythenorth> maybe it's just a bug? 21:43:47 <planetmaker> maybe :-) 21:43:51 * andythenorth -> bed 21:43:55 <planetmaker> I wonder where frosch123 is :D 21:43:56 <Supercheese> blame the butler, it's all Jenkins' fault 21:44:09 <andythenorth> at least that grf can be tested with now ;) 21:44:14 <planetmaker> the butler has little say in translations ;-) 21:44:18 <Supercheese> :P 21:44:22 <andythenorth> I can apply same approach to IH and other grfs 21:44:26 <Supercheese> but it's always the butler! 21:44:29 <andythenorth> good night 21:44:30 <planetmaker> it's all bound to the march of the eints 21:44:34 <planetmaker> g'night andythenorth 21:44:38 *** andythenorth has left #openttdcoop.devzone 21:49:16 <frosch123> oh, you were also trying stuff :p 21:50:37 <planetmaker> not really trying... but... adding a project with custom lang_dir 22:28:23 <frosch123> well, apparently my script fails hard on both the lang_dir and the base_lang stuff :p 22:29:37 *** gfhtrhth has joined #openttdcoop.devzone 22:30:01 <frosch123> omg.. 22:30:23 <frosch123> excellent :) reading stuff from files, validating it, but then not using it :p 22:31:31 <planetmaker> :-) 22:47:03 <planetmaker> good night 23:16:07 <DevZone> Project Finnish Rail Infrastructure - Rails build #62-push: SUCCESS in 36 sec: https://jenkins.openttdcoop.org/job/frissrails/62/ 23:22:59 <DevZone> Project Finnish Rail Infrastructure - Rails build #63-push: SUCCESS in 42 sec: https://jenkins.openttdcoop.org/job/frissrails/63/ 23:24:46 <DevZone> Project Fake Subways build #11-push: SUCCESS in 25 sec: https://jenkins.openttdcoop.org/job/fake-subways/11/ 23:25:59 <DevZone> Project FISH is ships build #15-push: SUCCESS in 1 min 13 sec: https://jenkins.openttdcoop.org/job/fish/15/ 23:32:13 <DevZone> Project OpenGFX build #32-push: SUCCESS in 6 min 13 sec: https://jenkins.openttdcoop.org/job/opengfx/32/ 23:34:05 <frosch123> ok, fish now uploaded 23:34:13 <frosch123> and i removed and reuploaded fake-subways 23:34:18 <frosch123> baselang is en_us now 23:34:27 <Supercheese> ah, I was wondering why it disappeared from eints 23:34:44 <Supercheese> I will remember to set baselangs properly at first commit next time ;) 23:47:52 <DevZone> Project OpenGFX+ Landscape build #9-push: SUCCESS in 23 min: https://jenkins.openttdcoop.org/job/ogfx-landscape/9/ 23:58:35 <frosch123> night 23:58:37 *** frosch123 has quit IRC