Re: translations again

On Tue, 21 Feb 2017, 23:37 Pedro Neves, wrote: > On 21-02-2017 21:28, Dirk Hohndel wrote: > > The question becomes: should I leave Transifex source strings unchanged, > > create a 4.6 branch, cherry pick the hand full of bug fixes in master > that > > came in since 4.6.2 (three commits from Linus

Re: Subsurface minimum gas calculation - First version for review

I can help testing this as I'm familiar with the Minimum deco or Rock bottom gas management. If you send me a link to your branch I can look at it and try to break it. Pablo On Tue, Feb 21, 2017 at 14:04 Stefan Fuchs wrote: > Hello Robert, hallo Dirk, > > Am 21.02.2017 um 11:44 schrieb Robert

Re: Subsurface minimum gas calculation - First version for review

> On Feb 21, 2017, at 2:04 PM, Stefan Fuchs wrote: > > Hello Robert, hallo Dirk, > > > Am 21.02.2017 um 11:44 schrieb Robert Helling: >> Stefan, >> >>> On 21.02.2017, at 11:02, Stefan Fuchs >> > wrote: >>> the problem is that for computers that don’t have gas infor

Re: German CCR divers wanted for question about how to translate "(CCR) setpoint"

Stefan, > On 21 Feb 2017, at 23:13, Stefan Fuchs wrote: > > How do German CCR divers call this correctly? My guess is that most of you > are using the English term "Setpoint", maybe in German with upper case "S"? > Or is there a widely used German term? I am not rebreather trained myself but

German CCR divers wanted for question about how to translate "(CCR) setpoint"

Hi All, stumbled across the fact that there are some different translations for the (CCR) "setpoint" used in Subsurface and this doesn't look nice to me. IMHO strange translations include: SetpointEinstellwert Setpoint fallbackErsatzeinstellwert Sample setpointEinstellwert des Date

Re: Subsurface minimum gas calculation - First version for review

Hello Robert, hallo Dirk, Am 21.02.2017 um 11:44 schrieb Robert Helling: > Stefan, > >> On 21.02.2017, at 11:02, Stefan Fuchs > > wrote: >> >>> the problem is that for computers that don’t have gas information, >>> the interpolation of cylinder pressures is only done at the

Re: translations again

On 21-02-2017 21:28, Dirk Hohndel wrote: The question becomes: should I leave Transifex source strings unchanged, create a 4.6 branch, cherry pick the hand full of bug fixes in master that came in since 4.6.2 (three commits from Linus, a couple from Robert, one from Jan) and create a 4.6.3 based

Re: translations again

Dirk, > On 21 Feb 2017, at 22:28, Dirk Hohndel wrote: > > The question becomes: should I leave Transifex source strings unchanged, > create a 4.6 branch, cherry pick the hand full of bug fixes in master that > came in since 4.6.2 (three commits from Linus, a couple from Robert, one > from Jan) a

translations again

Hi everyone... As I have pointed out a few times, I am planning to do another release in a week or so in order to get more complete translations to Greek and Italian, and in order to include the Catalan translation that I forgot to include in 4.6.2... but now I'm in an odd spot. There have been a

Prepare event names for translation

Hallo Robert, Am 21.02.2017 um 11:44 schrieb Robert Helling: > >> >>> And as I said: I think it’s cleaner to add an event to the dive >>> rather than plot directly to the profile. Simply use >>> >>> structevent*add_event(structdivecomputer*dc,unsignedinttime,inttype,intflags,intvalue,constchar*nam

Re: Subsurface minimum gas calculation - First version for review

Hallo Robert, Am 20.02.2017 um 15:18 schrieb Robert Helling: > Stefan, > >> On 20.02.2017, at 15:02, Stefan Fuchs > > wrote: >> >> Now I identified the next hurdle: Is there somewhere the curve >> cylinder pressure versus dive time for every specific cylinder? Or >> how coul