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
Translations? #89
Comments
yes - we definitely do need translation support - it would be a huge job though since there is lots of text. I dont know if its feasible but maybe with a bit of HTML knowledge could try to implement something like this? Maybe see if the button appears where the locale being used is not English |
As the parent fork of |
@lah7 that's very useful - many thanks. Hopefully someone could help with integrating translation support (pull requests) as this is an area we are not familiar with. |
I can work on integrating translation support the same way Ubuntu MATE Welcome does it (using po/pot files). Translators would use a tool named One thing to note - this involves surrounding your HTML with Which approach would you prefer for this project? |
@lah7 this would be brilliant if you are willing to-do this. Many thanks. Given that you said 2) is known to cause translations issues - 1) sounds the best. I presume Ubuntu MATE does it this way? If a pot file is available - we could just set up a project on launchpad so that people could submit via there? It would mean a manual transfer of .po files from launchpad to github - I've done this with two other projects I maintain. I see UB uses transifex - is this more popular with translators? I've never used transifex - is there people already signed up with transifex that can help translating - or does each project have to reach out themselves to find translators? |
No, we currently use (2) - it just means translators will inevitably raise issues to clarify the context, depending how many tags you have splitting them up. For example, in chatroom.pot:
(1) makes the context more obvious, but a mistake in translations could break HTML or expose the tags accidentally:
(I'm not sure if POT files can now specify context too?) The other way is to strip out any tags used in this fashion -- which may mean sacrifying pretty It's just standard pot/po files -- this produces one for each page, and another for the main Python file, so it's up to you how to manage translations.
Ubuntu MATE uses Transifex, which once set up, is actually easier to maintain -- as you can run commands to push/pull translations to/from Transifex. It's much simpler for translators. Not sure how popular it is, I know the rest of the MATE Desktop uses it too. Both MATE Desktop and Ubuntu MATE Welcome asked their communities (or have regular translators) to help with translating. |
ok - whilst I understand the issues over potential breakages - I consider context to be the most overriding issue here. Thus 1) is the best way to go. The benefit also is this forces us to check each page (there aren't many) to see that everything is ok - and importantly that the weblayout is consistent. In terms of specifying context with tags like zwnj - html tags only provide the ability to either translate - or not translate. We would have to invent a non-visible tag that is parsed by python and added to the pot file. Lets keep things as simple as possible. I'll have a think about launchpad vs transifex - thanks for the insights on how the MATE community does stuff. |
ok - in principal the basic translation stuff seems to work ok - obviously some issues to work through as seen in these two screen-shots (install spanish language - then before running ./budgie_welcome
@lah7 spanish html files were created in the data/i18n folder but no .po in ./locale. also no en_CA base html files in data/i18n but there is a en_CA.po in .locale. I'm confused - any thoughts what is going on here? |
Coincidentally, I had added en_ca in transifex when I was testing. It is likely unrelated (I have not yet read this thread), but wanted to flag that just in case the web hooks pushed it back while I was testing. But I do not think that is the case. |
That's because there is no
Hmm, I don't see any
☝️ In case the files are being put in the wrong places when syncing Transifex. For the "wrong" characters, I did notice this warning when running
But that would be for the main Python application, I don't know how to fix this. However, the HTML pages, I've fixed in this for you here. This happened with Ubuntu MATE Welcome, the HTML pages need a |
@fitojb I've added two more missing translation files - "default" and "recommendations". Please can you add approximately 5% or more spanish translations to these files so that I can continue testing the spanish version of budgie-welcome? TIA |
excellent - thanks @fitojb for the extra translations. These now enable the app to display in spanish. @niyasc any ideas how we can get the two buttons in blue on the initial welcome screen (see picture above) to autoexpand if the translation string is slightly too large ? both buttons will need to autoexpand equally - probably some sort of CSS magic?! |
@fossfreedom Currently, these two buttons are set to fill a boostrap grid having width 3 units(out of 12 units). So, if we adjust the button size to fill the content, we'll have to compromise with alignment of buttons. In that case, I was thinking about a vertical wrap. Alternatively, we may increase width of buttons and stack them vertically. But it won't be proportionate to length of text. |
@niyasc thanks for the feedback. I think maybe we should go back to the translator and ask that the translation string be made shorter. Two further thoughts though before that request - the capitalisation of the buttons ... why? that makes the number of chars to fit in the button slightly smaller than if mixed case. secondly The button width includes the icon - but you can see the actual number of chars for the text is much smaller than the other buttons on the screen. Maybe adjust the width to be the same as the other buttons ... and lose the icons ? EDIT: or maybe increase the size of the buttons from 3 units to 4? |
Btw, translation was not working for me. May be because, I don't have specific locale installed. I was getting this error message.
|
I had to-do the following:
if that still produces the same issue - then I've probably also installed spanish in my VM Think mixed case is better. The revised screenshot without the icons works for me. |
closing this. First Polish translation has been verified as working. |
This package is part of the first experience with Ubuntu Budgie. It seems to be untranslatable, and for first-time users it looks like we translators are sloppy.
The text was updated successfully, but these errors were encountered: