Messages

1

Translations / Re: French "close to original" translation

« on: October 11, 2018, 02:50:59 pm »

I checked Transifex, and it looks like TFTD is only 65 % translated in French. You can always join the team to help out with the translation. I don't know, where you can find the original translation, though. :c

2

Translations / Language support for "stock" mods ("Aliens pick up weapons" etc.)

« on: September 23, 2018, 01:19:24 pm »

Hi!

I was wondering if the stock mods included in the base OpenXcom package (such as "Aliens pick up weapons", "Xcomutil: Improved heavy laser" and so on) could have language support added for them and be included in Transifex?

Sorry, if this has been discussed elsewhere already.

3

Translations / Re: Soft hyphens

« on: March 23, 2016, 10:06:05 pm »

You know that's the thing that kept shining through when I was translating TFTD compared to EU: the inferior writing. It's less believable in many ways. One thing is the scientific aspect you guys mentioned, and then there's the overall writing style, which just seems so unprofessional and off-the-record, with Ufopedia descriptions brimming with stuff that shouldn't be written in scientific/technical reports for a top-secret military organisation, such as the gas cannon being a favourite amongst experienced aquanauts. This kind of writing is more suitable for a horror novel than a technical report.

Feels like the developers sacrificed also on the believability of the writing when trying to focus on the atmosphere and setting of the game. Or then they just had to develop the game so fast that they didn't have time to realize how cheesy their writing was for them to edit it.

4

Translations / No string for '$1000's' in Transifex

« on: March 19, 2016, 11:26:21 am »

I noticed while testing my translation, that the "$1000's" text that appears above the graphs isn't in Transifex. Could it be added, please?

5

Translations / Soft hyphens

« on: March 18, 2016, 09:48:37 pm »

Would it be possible to add support for conditional hyphenation? A case in point would be screenshot1, which is the Ufopedia entry on the Gauss Rifle in Finnish. As you can see, the third row has very little text because the word on the fourth row (twin particle accelerators in Finnish) can't fit on the same row, resulting in aesthetically very unpleasant layout.

But I wouldn't ask about this if it was only about the aesthetics, but this inefficient use of text space becomes a problem in longer Ufopedia entries, such as on the Medi-kit (screenshot2). I was only able to fit in the text after I had simplified the translation and adding a couple of hyphens on the words 'haavoja' and 'tajuttoman' (on rows 5 and 11 respectively) by typing 'haavo-ja' and 'tajut-toman' in Transifex.

Now even this won't be a terrible problem, as long as in the later builds there will be no adjustments in the Ufopedia text box dimensions. But that is a completely unreasonable requirement. As soon as adjustments occur in the text boxes, the layouts for these manually hyphenated texts will go out of whack, where in this case 'haavo-ja' and 'tajut-toman' appear completely stupid.

So, if it's not too much trouble, would it be possible to add conditional hyphenation, where OpenXcom will recognize a certain symbol in Transifex as a conditional hyphen that will only be added ingame, if the particular word won't fit at the end of the row? In this case I'd type 'haavo{chyphen}ja' and 'tajut{chyphen}toman' in Transifex, or whatever symbol we choose to use (just like there are things like {newline} and whatnot).

I know that this may not be a big problem in English, for example, with many short words, and where compound words have spaces in them, unlike in Finnish, where 'post office' would be written in the style of 'postoffice' with no space between the component words. Just look at screenshot1 again with the Finnish equivalent of the twin particle accelerators and you can see how that can be a problem.

EDIT: Hmm, maybe I should have posted this in the troubleshooting section instead, or something. Maybe a mod could help me out with that?

EDIT 21.3.2016: And maaaaybe I should have checked Wikipedia first before coming up with the original thread name "Conditional hyphenation". In Wikipedia conditional hyphens are called soft hyphens, so I renamed the thread to "Soft hyphens". You can read more about them on Wikipedia:

https://en.wikipedia.org/wiki/Soft_hyphen

6

Work In Progress / Re: Mod Translation Project

« on: March 18, 2016, 08:06:36 pm »

Sorry, if I simply haven't lurked enough, but has this idea materialized? I'm just asking, because in the current nightly builds, many of the things that used to be in the ADVANCED settings (such as TFTD damage model), have now been moved to the MODS section, and the mod descriptions aren't available for translation in Transifex (and I NEED my daily fix of translating OpenXcom).

Even if a global mod translation project doesn't become a reality, I'd like that at least these 'vanilla' mods, that ship with OpenXcom, could be added to Transifex and be translated. 

7

Translations / Re: Translating the Windows Installer

« on: May 19, 2014, 03:58:34 pm »

Hi!

Here's the Finnish version:

Code: [Select]

;--------------------------------
;Pages

LangString PAGE_UfoFolder ${LANG_FINNISH} "${GAME_NAME} edellyttää pelin UFO: Enemy Unknown / X-COM: UFO Defense alkuperäiskappaleen omistamista. Voit ohittaa tämän vaiheen, jos olet päivittämässä aiempaa asennusta.$\n$\nAsennus kopioi vaadittavat tiedostot seuraavasta kansiosta. Kopioidaksesi toisesta kansiosta napsauta Selaa ja valitse toinen kansio. Napsauta Seuraava jatkaaksesi."
LangString PAGE_UfoFolder_TITLE ${LANG_FINNISH} "Valitse X-COM 1:n sijainti"
LangString PAGE_UfoFolder_SUBTITLE ${LANG_FINNISH} "Valitse kansio, johon X-COM 1 on asennettu."
LangString DEST_UfoFolder ${LANG_FINNISH} "X-COM 1:n kansio"

;--------------------------------
;Installer Sections

LangString NAME_SecMain ${LANG_FINNISH} "Pelin tiedostot"
LangString DESC_SecMain ${LANG_FINNISH} "Vaadittavat tiedostot ohjelman ${GAME_NAME} ajamiseksi."
LangString NAME_SecPatch ${LANG_FINNISH} "Datakorjauspäivitys"
LangString DESC_SecPatch ${LANG_FINNISH} "Korjaa virheitä X-COM 1:n datassa. Suositellaan ensiasennuksen yhteydessä. (Vaatii Internet-yhteyden)"
LangString NAME_SecDesktop ${LANG_FINNISH} "Työpöydän pikakuvake"
LangString DESC_SecDesktop ${LANG_FINNISH} "Luo työpöydälle pikakuvakkeen pelin ${GAME_NAME} pelaamiseksi."

;--------------------------------
;Uninstaller Descriptions

LangString NAME_UnData ${LANG_FINNISH} "Poista X-COM:n tiedot"
LangString DESC_UnData ${LANG_FINNISH} "Poistaa kaikki ohjelman ${GAME_NAME} tiedot, mukaan lukien modit ja X-COM-resurssit. Suositellaan puhtaan uudelleenasennuksen yhteydessä."
LangString NAME_UnUser ${LANG_FINNISH} "Poista käyttäjän tiedot"
LangString DESC_UnUser ${LANG_FINNISH} "Poistaa kaikki ohjelman ${GAME_NAME} käyttäjän tiedot, mukaan lukien tallennetut pelit, kuvakaappaukset ja asetukset. Suositellaan täydellisen poiston yhteydessä."

;--------------------------------
;Shortcuts

LangString LINK_DataFolder ${LANG_FINNISH} "Datakansio"
LangString LINK_Readme ${LANG_FINNISH} "Lueminut"
LangString LINK_UserFolder ${LANG_FINNISH} "Käyttäjän kansio"
LangString LINK_Uninstall ${LANG_FINNISH} "Poista"

;--------------------------------
;Warnings

LangString WARN_UFOMissing ${LANG_FINNISH} "X-COM 1:stä ei löytynyt tästä kansiosta. ${GAME_NAME} vaatii kelvollisen asennuksen X-COM:sta toimiakseen. Jatketaanko?"
LangString WARN_XCUDetected ${LANG_FINNISH} "XcomUtil havaittu. ${GAME_NAME} ei ole yhteensopiva XcomUtilin kanssa, mikä saattaa aiheuttaa häiriöitä pelin toiminnassa. Jatketaanko?"


8

Troubleshooting / Re: Line breaks in long strings

« on: May 15, 2014, 08:26:35 am »

Ugh, I just realized I should have probably written this in the bug tracker. >_> I filed the issue there instead, so you can close this thread.

Sorry!

9

Troubleshooting / Line breaks in long strings

« on: May 15, 2014, 08:17:23 am »

Hello,

I have a little suggestion to improve the aesthetics of line breaks in long strings. The problem is that when OpenXcom makes a line break in a long string, it adds the space to the new line instead of the previous line (see pictures) creating an unnecessary indentation. It's not that common in the English version, but a bit more common in the Finnish translation for the strings to wrap to another line, so it would be nice if someone had the time to fix the line breaking rules to include the space at the end of the word preceding the line break.

Thanks a lot for your great work on this marvellous gem, guys!

10

Fan-Stuff / Re: Soldier names

« on: May 15, 2011, 03:22:11 pm »

Hi, everyone!

Not a coder here, but I'd like to contribute by adding Finnish names. I like RyanCrierie's idea. In addition to the region of the base, the population size of the country could also affect the probability of an individual name set, if it's okay.