[PATCH] Updated Finnish translation

Miika Turkia miika.turkia at gmail.com
Sun Oct 21 13:11:11 PDT 2012

On Sun, Oct 21, 2012 at 10:17 PM, Dirk Hohndel <dirk at hohndel.org> wrote:
> On Oct 21, 2012, at 12:14 PM, Miika Turkia wrote:
>> On Sun, Oct 21, 2012 at 9:47 PM, Dirk Hohndel <dirk at hohndel.org> wrote:
>>> Miika Turkia <miika.turkia at gmail.com> writes:
>>>> On Sun, Oct 21, 2012 at 8:17 PM, Dirk Hohndel <dirk at hohndel.org> wrote:
>>>>> On Oct 21, 2012, at 6:40 AM, Miika Turkia wrote:
>>>>>> I have no idea why, but the filters are not translated for me.
>>>>> I think that's the problem Linus pointed out.
>>>>> You are getting them (in English) from your XML file.
>>>> Yep, that sounds like the reason. And that also explains the capital
>>>> words that I could not find from the sources.
>>> Please try again with the latest master. I think with my patches you
>>> should now see translated strings.
>> Now the filters and tooltips are translated. However, I still have a
>> few English words in the filters: SLOW, DECO, ATTENTION. My guess is
>> that these capitalized forms got to the log files from XML
>> transformations when switching from JDiveLog to Subsurface. At least
>> opening my old JDiveLog log with Subsurface I get these alarms in
>> capital. Capital texts from XML transformations is probably somewhat
>> common phenomenon for people switching to Subsurface.
> Interesting. Not sure what to do about this - because if you think about it,
> an XML file that comes from different software could contain all kinds of
> texts - and we have no way of knowing what they are. So how would we
> add them to our text data base and have them translated?
> I don't think I know a real solution to this.
> I guess one option would be an XML transformation file that we maintain
> that matches known strings from other dive log software to our strings
> and tell users to run this against their XML file if they want their "old" events
> localized as well?

The transformation file used to read alien dive logs should take care
of the mapping of events. In this case jdivelog2subsurface.xslt should
be updated. I'll send a patch for that. However, I am not sure if
*attention* is same as *violation*.

I guess it would not hurt to have another transformer for fixing log
files afterwards for cases like mine (even though sed will fix my logs
just fine).


More information about the subsurface mailing list