IRC logs for #openttd.dev on OFTC at 2014-06-20
⏴ go to previous day
09:30:01 *** Zuu has joined #openttd.dev
15:06:18 *** frosch123 has joined #openttd.dev
15:06:18 *** ChanServ sets mode: +v frosch123
17:32:55 *** Alberth has joined #openttd.dev
17:32:55 *** ChanServ sets mode: +v Alberth
17:38:23 <planetmaker> https://bugs.openttd.org/task/6044 <-- would suffice a proper check for a multiplayer situation, right? Or should we make the check even more tight and make it an actual command (IMHO not)?
17:43:24 * Alberth doesn't know how it changes production
17:45:10 <Rubidium> planetmaker: it should've been a command all the way anyhow
17:53:54 <frosch123> depends on whether you only want to prevent that cheat
17:54:01 <frosch123> or whether you also want to disable the other ones
17:55:46 <frosch123> looks like magic_bulldozer, crossing_tunels, no_jetcrash and setup_prod have effecs outside the cheat gui
17:55:56 <frosch123> i guess setup_prod is the only one that desyncs
17:56:03 <frosch123> the others are just cheats :p
17:56:50 <frosch123> i guess that diff is fine (minus the config.lib)
18:09:59 <planetmaker> Rubidium, why do we need it as a command? You mean shared with the industries changing productions themselves?
18:10:57 <frosch123> it would need to be a command if it should work in multiplayer
18:11:14 <frosch123> but i actually would not trust that anyway to not cause havoc with weird grfs
18:11:22 <Rubidium> conceptually everything that modifies the game state should be a command or setting (and settings are already changed by commands)
18:11:42 <Rubidium> and commands we can just disable in network by means of the flags
18:14:28 <Rubidium> (modifies game state directly triggered by a human or AI)
19:12:44 *** Supercheese has joined #openttd.dev
19:12:44 *** ChanServ sets mode: +v Supercheese
19:44:39 <planetmaker> I'd commit my GUI fix and for now add a todo as to where the command would need calling for FS6044. Is that acceptable?
19:45:27 <planetmaker> *a TODO comment in the code
19:51:29 <frosch123> i actually wouldn't bother with the command
19:51:55 <frosch123> noone will work on that anyway
20:26:50 <planetmaker> the same string replacement for the other languages, but not shown here for clarity's sake
20:28:05 <planetmaker> actually for other languages translators have to translate the ordinal numbers, not the day numbers
20:28:14 <planetmaker> (less tedious, that's why)
20:28:28 <frosch123> misses a "#### range ends here" for the ordinal numbers
20:28:43 <Rubidium> technically you should be able to clone the strings with sed in the other languauges
20:28:44 <frosch123> not that it has a meaning, but i think it is used that way
20:28:47 <Rubidium> (order doesn't matter)
20:28:58 <Rubidium> then I can trigger a WT3 commit to clean everything up
20:29:35 <planetmaker> Rubidium, you mean just copy/rename them unorderly for other languages and WT3 will cleanup order?
20:29:49 <frosch123> there are too few spaces for indenting the ":", aren't there?
20:30:56 <Rubidium> the order of strings in the translation doesn't even matter at all
20:30:56 <planetmaker> ok, then I'll dup that for the other languages, too
20:37:23 <planetmaker> do you have the sed regex at hand for that copy&rename, Rubidium ?
20:38:53 <frosch123> s/STR_ORDINAL_NUMBER\([^ ]*\)\(.*\)/&\nSTR_DAY_NUMBER\1 \2/
20:39:36 <Rubidium> someone was quicker ;)
20:39:37 <frosch123> just make a backup of english.txt in advance
20:39:59 <frosch123> in a different directory, resp. with a different file extension
20:40:02 <Rubidium> and don't forget the unfinished languages ;)
20:40:36 <frosch123> usually i copy english.txt to src, run sed on all txt in lang and unfinished, and copy english.txt back
20:41:29 <frosch123> i wonder whether there is some mobile game, where you assemble regular expressions against the clock :)
20:42:39 <planetmaker> would be a market niche ;)
20:45:16 <frosch123> hmm, there are regex crossword puzzles
20:45:48 <frosch123> fill in letters, so all expressions match :)
20:46:00 <frosch123> but, that is kind of the inverse
20:46:57 <frosch123> hmm, searching for sed games only results in games written in sed :s
20:47:14 <planetmaker> you probably need to search for regex game or so
20:47:30 <frosch123> yup, that was my first
20:47:38 <frosch123> but it is only about matching
20:47:41 <frosch123> not about transformation
20:47:42 <planetmaker> hm, will I kill the 1 pending estonian string when I commit now?
20:48:03 <frosch123> depends whether you modify the same string :)
20:54:58 <Rubidium> it (still) barfs on reading back commits where something with cases changes
20:56:18 *** Alberth has left #openttd.dev
21:03:46 <Rubidium> it's a heavy one for WT3 to stomach
21:04:34 <planetmaker> yes. Took already quite some time to commit. And FS was slow then, too :)
21:09:06 <frosch123> do you want that stuff in 1.4 ?
21:09:47 <planetmaker> he, good question. You can argue it both ways.
21:10:00 <planetmaker> Only if it's not much trouble, I think
21:10:01 <Rubidium> given the meaning of the string changed, I guess it's best to have it. Just backport the cpp and english.txt change
21:10:09 <frosch123> no, i mean whether rb is interested in the regex challenge :)
21:10:44 <frosch123> though i already backported the STRINGx fixes
21:20:06 <Rubidium> reloading estonian...
21:20:20 <planetmaker> whopping big commit
21:23:05 <Rubidium> ~650 k for string backports
continue to next day ⏵