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

Placeholders for .po source to .xml and .strings files #7788

Open
2 tasks done
keikoang opened this issue Jun 20, 2022 · 4 comments
Open
2 tasks done

Placeholders for .po source to .xml and .strings files #7788

keikoang opened this issue Jun 20, 2022 · 4 comments
Labels
enhancement Adding or requesting a new feature. undecided These features might not be implemented. Can be prioritized by sponsorship.

Comments

@keikoang
Copy link

Describe the issue

Hello, our translation files in Weblate are based in .po and they are the base for translating to Android .xml and iOS .strings. We have configured $STRING$ for string placeholder, as in the screenshot below
image

When exporting to Android .xml we want the $STRING$ to be converted to %s while exporting to iOS .strings, we want the $STRING$ to be converted to %@. Is there a way to make this happen without having two different translation projects/components, one for Android, and the other one for iOS?

I already tried

  • I've read and searched the documentation.
  • I've searched for similar issues in this repository.

Steps to reproduce the behavior

Configure any placeholders in the settings
image

Expected behavior

When exporting to Android .xml we want the $STRING$ to be converted to %s while exporting to iOS .strings, we want the $STRING$ to be converted to %@. Is there a way to make this happen without having two different translation projects/components, one for Android, and the other one for iOS?

Screenshots

No response

Exception traceback

No response

How do you run Weblate?

Docker container

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

@keikoang keikoang added the question This is more a question for the support than an issue. label Jun 20, 2022
@github-actions
Copy link

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.

In case your question is already answered, making a donation is the right way to say thank you!

@nijel
Copy link
Member

nijel commented Jun 20, 2022

Weblate doesn't support any such conversions.

@github-actions

This comment was marked as off-topic.

@github-actions github-actions bot added the wontfix Nobody will work on this. label Jul 1, 2022
@nijel nijel added enhancement Adding or requesting a new feature. undecided These features might not be implemented. Can be prioritized by sponsorship. and removed question This is more a question for the support than an issue. wontfix Nobody will work on this. labels Jul 1, 2022
@github-actions
Copy link

github-actions bot commented Jul 1, 2022

This issue has been put aside. It is currently unclear if it will ever be implemented as it seems to cover too narrow of a use case or doesn't seem to fit into Weblate.

Please try to clarify the use case or consider proposing something more generic to make it useful to more users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adding or requesting a new feature. undecided These features might not be implemented. Can be prioritized by sponsorship.
Projects
None yet
Development

No branches or pull requests

2 participants