Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add fully translation capabilities on the locations sheet #1042

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sharak
Copy link
Contributor

@sharak sharak commented Feb 13, 2025

Hi friend.

This PR adds translation keys for fully i18n on the locations sheet. I don't know if this approach is ok for you. Maybe there are too many oracle titles in the translation file... I don't know.

If you would like a different approach, please let me know.

Copy link
Owner

@ben ben left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great, long overdue. Thanks!

@@ -355,13 +442,13 @@ const oracles = computed((): OracleSpec[][] => {
return [
[
{
title: 'Atmosphere',
title: game.i18n.localize('IRONSWORN.LocationOracleNames.Atmosphere'),
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually on a second look, these aren't quite right. The real correct way here is to let a Babele module do these translations, which means using the name from the compendium pack (probably via an index). Let's keep the values above, and drop the changes for individual oracles (anything with a dsid field) for now, we'll come back and fix it later.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Of course.

I supposed that it was the right approach. Maybe I could thinking on it and update the PR. It is ok for you?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes please!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have encountered some problems that I don't quite know how to solve. I'm still a bit lost with the structure of the oracles in datasworn. Maybe you can help me.

The problem appears, for instance, in the settlements. When we select a settlement type location the dsid for population is:
oracle_rollable:starforged/settlement/population/${rc} where rc is the chosen region.

If we pass that id through the OracleTable.getByDsId function we get that the name is "Outlands" instead of "Population". But there is not a proper oracle for Population, it depends on the selected region.

Do I make myself clear? How could we manage this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants