Ludeon Forums

Ludeon Forums

  • July 02, 2022, 07:17:54 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Arczi008TV

Pages: [1] 2
Bugs / Translation problems and bugs
« on: August 29, 2021, 01:29:58 PM »
Some bugs, and problems.


Previously <PawnMainDescGendered> was working fine,
but now {0} in <PawnMainDescFactionedWrap> is always: {PAWN_gender} {1}.
And <PawnMainDescGendered> doesn't seem to affect anything.


Maybe im wrong but Male stallion sounds weird, like there is female stallion.
I think animal name should be taken from label - HORSE if there is a different names depending on their gender.
Jasper (male horse) or Jasper (stallion)


Its using <Male> and <Female> instead of <MaleAnimal> and <FemaleAnimal>
So in many other languages its displayed wrong.


Can you fix default language worker or add second default with correct letter sizes?


{PAWN_gender} is working in social opinion about colonists,  after adding new line with Social at end, like this  <....labelSocial>
Gender symbol is working in mood too but its not defined, its called label only <....label> could be <....labelMood >

And that causing problem with displaying moods in ideology customization.
Why? Because it is taken from <....label> with gender symbols (which works in game).

This need separate code

Could be 3 types:
Label - colonist mood display and things in menu
Mood -I have tried adding <AteInsectMeatDirectMood.stages.ate_insect_meat.label> but not working.
Social - already there :)


... We now support "numCase" and "replace" resolvers natively and every language can use them. You could take a look at the Russian language for an example.

numCase not working, also not working on russian without language worker

Translations / Re: Request: Help check the language workers for accuracy
« on: August 21, 2021, 01:32:28 PM »
Thanks for posting the LanguageWorker! However, since 1.3 we've introduced a new system which makes such custom code unnecessary. We now support "numCase" and "replace" resolvers natively and every language can use them. You could take a look at the Russian language for an example.

numCase not working for me

And what about fraction & world map names? In english language worker its uses Big Letter Size
With default worker, or without:     Only first word is big

Translations / Nephew/niece translate problem
« on: August 04, 2021, 01:10:56 PM »
So nephew is a son of my brother/sister
In english its single word, but in other languages it may be 2 words.

 <MyNephewLost.stages.my_nephew_lost.label>My nephew1/nephew2 {0} lost</MyNephewLost.stages.my_nephew_lost.label>

Can you extend that to something like this:
<NephewOfMyBrother.label>Nephew1  <-- nephew borned by my brother
<NephewOfMySister.label>Nephew2 <-- nephew borned by my sister

Or there already is a way to do it?

Translations / Re: New keyed translations format
« on: July 31, 2021, 01:54:10 PM »
Hmm, I understand. Some nouns are always plural..

Rice and corn is always plural in my language, but still rice is male and corn is female.

Problem is here. <RawPotatoes.label>Potatoes</RawPotatoes.label>
We can have one potatoe in storage. But you recieve letter:  "Potatoes has rotted away in storage."

So if you could do something like this. (that propably would be easy to do)

And then use:
  <MessageRottedAwayInStorage>{1_label} {1_gender ? A : B : C} has rotted away in storage.</MessageRottedAwayInStorage>
  <MessageRottedAwayInStoragePlural>{1_labelPlural} {1_gender ? A : B : C} has rotted away in storage.</MessageRottedAwayInStoragePlural>

We could use also
{0_labelPlural} like there is {0_kindPlural}: humans, cats, dogs (kind label (plural)

Translations / Re: Gender code problem, still not fixed
« on: July 31, 2021, 12:12:47 PM »
Good, but topic its about that not working here.

So [Bodypart] its propably not working because of mistake.
And my solution is not working well too.  Because its about special characters, they are wont work on planet view. Even if you put them in custom txt file.

If you create
<li>boDy_paRt->Words/Nouns/BodyPartFile</li> you have to use [boDy_paRt] because letter size matters.

I think its caused by cyrylic special characters:
 "%u0105" , "%u0119" (oh even in this forum that characters causing bug xd)

After translating "RulePacks_Namers_WorldFeatures.xml"

or if you put special characters in txt files in string folder, it cause that error.

No solution. Need wait for fix.

We can't use cyrylic special characters in everything that is relatet to planet view, because it causing errors.
-But chinese characters and symbols like this "•◘♦☺☻♥" working ok.

Bugs / Small letters problem on v1.1
« on: March 01, 2020, 10:12:16 AM »
Something is wrong. Now small letter is not converted to big properly in some cases.

It affects translations quality
On 1.0 it was correct.

Translations / Re: Translation cleaner problem in v1.1
« on: February 28, 2020, 04:00:54 PM »
I hope it won't be too hard to do a find/replace on them.
When something is marked as 'unused' we dont know it is deleted or moved to another file or code is renamed. That is a little bit confusing.

PS. Can you add polish language worker?

Translations / Re: Request: Help check the language workers for accuracy
« on: February 27, 2020, 12:29:00 PM »
Yes, add above language worker

Translations / Re: Official: Polish
« on: February 26, 2020, 01:06:41 PM »
Trudne jest spolszczenie czegoś co nie jest do tego przystosowane. A po za tym już jest wersja 1.1.

Stan tłumaczenia w grze jest nieaktualny. Aktualne spolszczenie trzeba pobrać ze strony:
bezpośredni link:

Dopóki nie będzie się dało po ludzku przetłumaczyć, dotąd się nic rewelacyjnego nie pojawi.

Translations / Translation cleaner problem in v1.1
« on: February 26, 2020, 03:43:17 AM »
This tool is making now unnecessary mess.

Previously code
<NeurotrainerUsed>{USER_labelShort} used {1} neurotrainer to go from level {2} to level {3}</NeurotrainerUsed>

After using cleaner, that appear:
It should just update.

Backstories.xml after cleaning is like destroyed.

<AbandonedChild47> is changed to <AbandonedChild30> and translation is DELETED, just TODO appear.

Or translation is moved in wrong place!
Translated <Abductee80> is now in <Abductee43> which has different text to translate.

Translations / Re: English translation mistake
« on: November 10, 2019, 04:10:21 PM »
Also this.

Pages: [1] 2