IMPORTANT: due to a GitHub incident (https://www.githubstatus.com), you might not be able to use GitLocalize for a while. Let's hope this gets resolved soon.
Hi everyone. I need your help. I'm getting to use GitLocalize. Everything works fine with my personal repository from my Github account. However, I cannot manage to add a repository from my Organization, not only me but also the Admin repo, and pretty sure that the application is installed in the setting. When I press the submit button, it seems to be in the loading stage forever without any errors. Thanks in advance! :)
nvm found it!
Hi I'm trying to setup Japanese translations onto a project through GitLocalize, but it tells me that the project needs to be in sync continuously. We cannot access the area where the documentation can be translated. We have three people on the GitLocalize project currently. Has anyone experienced this issue?
I reported this on Github as a bug but also posting about it here in case there is another solution. We just fully started using GitLocalize to translate our software documentation a few weeks ago. For 2 files in 1 document, the translation was made, a review request was sent, the review was done, a pull request was made, the pull request was merged, and the translation was synced. Yet, the "Create Review Request" button appears beside the 2 files, even though the workflow is complete and there is nothing new to review. Have others had this problem?
Here is a link to our GitLocalize repo: https://gitlocalize.com/repo/4035/fr/admin-guide/en - you can see the "Create Review Request" button next to the files single-sign-on and appendix-1.
I added a comment to this issue, since it looks like the same one: gitlocalize/feedback#69
Hi everyone.I always get a Application error page when trying to access the language page of project.https://gitlocalize.com/repo/4984/zh(when I click the language button).The page get slow down when I click it.About half minute later,the application error page shows.It seems like occurs timeout.Is there anyone could help me fix it ?Thanks
Hi, someone in our issues queue recommended us to use GitLocalize, but our translation project uses GitBook.com too and the latter uses branches for translations. I see there's no option to use a branch as the translation destination in the GitLocalize config, but would using the same source and destination work?
Meaning I would just set it up from the translation branch directly, and never really touch the root language branch (English in our case)
I should clarify that this is a repository only for user manuals, so it makes relative sense to have branches for languages, as the application itself does not need access to those files. Only GitBook.
@ywarnier Hi, thanks for reaching out. Right now we only support the same branch for the source and the target files (translations). So indeed, a typical path setup usually looks like this: repo\branch\path\en for the source files and repo\branch\path\%lang% for the target files.
We are now working on a feature to support different repositories for source and target files, to support something like this:
repo1\branch1\en for source and repo2\branch2\%lang% for target. In this case you would be able to have repo\branch1\en and repo\branch2\%lang%
I'm not sure we will be able to support different branches for different languages at this point. I understand this is exactly the case with GitBook? We should discuss this internally though.
We are now working on a feature to support different repositories for source and target files, to support something like this:
repo1\branch1\en for source and repo2\branch2\%lang% for target. In this case you would be able to have repo\branch1\en and repo\branch2\%lang%
I'm not sure we will be able to support different branches for different languages at this point. I understand this is exactly the case with GitBook? We should discuss this internally though.
@ilyaspiridonov Yes, Gitbook uses something they call "Variants" which they recommend to manage translations. These "variants" translate, with their Github integration, to a branch in the repository you are using to generate the documentation. See https://docs.gitbook.com/editing-content/variants ("Variants are also be used to offer several translations of your documentation."). Their documentation's "Internationalization" section (https://docs.gitbook.com/features/internationalization) is unrelated though (it's about having the translation UI in a different language).
The idea behind Gitbook is to enable the generation of user guides and stuff like that, so I understand it's not the same primary focus as GitLocalize (which is fine by me). I just thought I'd ask and let you know this is a use case, but there's no big rush for us: using Git directly is relatively fine. I guess the workflow for tracking changes is suboptimal, but it's also less of a worry in a "user guide" context, because user guides don't have to be exactly synchronized all the time.
The idea behind Gitbook is to enable the generation of user guides and stuff like that, so I understand it's not the same primary focus as GitLocalize (which is fine by me). I just thought I'd ask and let you know this is a use case, but there's no big rush for us: using Git directly is relatively fine. I guess the workflow for tracking changes is suboptimal, but it's also less of a worry in a "user guide" context, because user guides don't have to be exactly synchronized all the time.
@spacecabbie Hi, I understand you need help with proofreading completed translations? Can you please send me more details at ilya@gitlocalize.com ? Including the link to the project. Thank you!
@dnjstlr555 What kind of search would you be interested in: within a file / across the entire project / anything else?
Can you provide more context as to what is happening: are you changing the file on github, or are you updating translations on GitLocalize? Maybe a link to a file? Thank you!
Can you provide more context as to what is happening: are you changing the file on github, or are you updating translations on GitLocalize? Maybe a link to a file? Thank you!
@ilyaspiridonov I changed GitLocalize generated language folder contents directly on github, for example https://github.com/dnjstlr555/staxel_korean-alpha/tree/lang
There's a folder named ko, which is generated by GitLocalize. I already translated some of files before I add repo to gitlocalize so in order to combine my translations I had to directly edit those files. But after I edited on github there's old entries remained on GitLocalize.
I know it's conflicting situation so I suggest that if there's searching feature within a file/entire project, It would much better for advancing translation. especially I have over 20k entries and all sorted little bit randomly.
I think within a file or entire project both will okay.
There's a folder named ko, which is generated by GitLocalize. I already translated some of files before I add repo to gitlocalize so in order to combine my translations I had to directly edit those files. But after I edited on github there's old entries remained on GitLocalize.
I know it's conflicting situation so I suggest that if there's searching feature within a file/entire project, It would much better for advancing translation. especially I have over 20k entries and all sorted little bit randomly.
I think within a file or entire project both will okay.
Hello, I am reaching out to ask about alt text support in GitLocalize. A translator today reached out to me to point out that images with alt text will sometimes behave oddly - images will appear normally in the source section, but if the corresponding segment is opened in the target, the incorrect segment text will display. Furthermore, this will sometimes cause images to display a variety of strange behaviours such as suddenly appearing as broken, being replaced by {img} tags on the source side, or becoming inaccessible on the target side by simply displaying a broken image symbol and the alt text that cannot be opened for editing. I am happy to provide a demo or screenshots if needed.
I have transfered ownership of the repository to an organization and now i cant delete the repsitory at all, nor i can create a new repository for the new organization
Hi I have a similar issue. https://gitlocalize.com/repo/5480 I also tried deleting the repo from github, but it didn't solve the issue.
@dnjstlr555 sorry for the long wait and thanks for the feedback! In principle, when you edit anything on github (source texts or translations), the changes should be synced back into the project - because Github is always the source of truth. We may have had some maintenance works when your project was syncing, so maybe that's why this did not happen in your case.
AS for the searching feature, we have added this to our roadmap, thank you!
AS for the searching feature, we have added this to our roadmap, thank you!
@emmauhl does the issue still get reproduced? we have fixed some bits related to images. can you please send a link to the file where you're experiencing this? thanks!
@ilyaspiridonov Thanks for responding! Yes, the issue persists - please take a look here and hopefully you will see the image/alt related issues pop up (especially when opening the segment for editing): https://gitlocalize.com/repo/4035/pt/accessible-content/en/galleys.md
console-tests.md and encryption.md
1 reply