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

Is keeping DE and IT doc right? #88

Open
techexo opened this issue Mar 19, 2019 · 15 comments

Comments

Projects
None yet
5 participants
@techexo
Copy link
Contributor

commented Mar 19, 2019

Hi everyone,

I was wondering if keeping the German (DE) and Italian (IT) documentation was still relevant... I don't think a lot of people willing to install wallabag on their/some server don't read English at all, and the translations seem to have dropped behind.

I can understand having the French one as most (all ?) of the core developers (and contributors?) are French. At some point, however, shouldn't we concentrate on fewer languages with better quality; and not have obsolete docs?

I don't want to bite the hand that feeds me (cracher dans la soupe), it's just that it seems like an interesting thinking to have.

@tcitworld

This comment has been minimized.

Copy link
Member

commented Mar 19, 2019

We could add a warning on top of other translations than french and english to say that these versions are probably outdated.

@techexo

This comment has been minimized.

Copy link
Contributor Author

commented Mar 19, 2019

Sounds like a good idea. I think a warning on top of all the pages would be the way to go (so people coming directly via a search engine will definitely see the warning)

@j0k3r

This comment has been minimized.

Copy link
Member

commented Mar 21, 2019

I'm wondering if we should just remove them?
For example, I'm an italian who want to check something in the doc. If I see a message saying it's outdated, I won't read the italian version but the english one. Nope?

@techexo

This comment has been minimized.

Copy link
Contributor Author

commented Mar 21, 2019

Honestly I think these extra translations are more a burden than useful: it's outdated, and I am pretty sure anyone wanting to actually host wallabag will speak at least technical English.

Could it be possible to "branch them out", so that someone wanting to update the whole doc could find them easily, but it isn't read by gitbook?

Edit: it's not really my place to say, but I think the issue could be extended also to French documentation... The actual question is, in my opinion, does having extra translations impeeds contributions to the doc (in the sense that a contributor feels obliged to translate in their language, and is discouraged by the task)?

@j0k3r

This comment has been minimized.

Copy link
Member

commented Mar 21, 2019

Maybe we should update the LANGS.md file and try locally.

@techexo

This comment has been minimized.

Copy link
Contributor Author

commented Mar 21, 2019

@j0k3r cf also edit of my post above

@Kdecherf

This comment has been minimized.

Copy link

commented Mar 22, 2019

Hello there,
Do we have usage statistics of the documentation pages?

@techexo

This comment has been minimized.

Copy link
Contributor Author

commented Apr 7, 2019

@Kdecherf Not that I know of. (But why would I? My answer is just a ping 😄)

@Kdecherf

This comment has been minimized.

Copy link

commented Apr 8, 2019

@techexo yeah, the question was for @j0k3r and @tcitworld :p

@j0k3r

This comment has been minimized.

Copy link
Member

commented Apr 8, 2019

oh sorry, I've no idea 🤷‍♂

@techexo

This comment has been minimized.

Copy link
Contributor Author

commented Apr 8, 2019

To reiterate my position, I think we should just keep one documentation, at least for the administration part.
I can understand keeping the FR one for the user part, as most users of wallabag.it are probably French, but the EN version is probably enough for people willing to install wallabag on a dedicated server.

If the EN version is sufficiently up-to-date, probably people will be willing to translate that in French and make a beautiful tutorial post on their blogs ;)

@j0k3r

This comment has been minimized.

Copy link
Member

commented Jun 5, 2019

As per answer to the main question I think we can keep only the FR & EN up to date and remove other. I don't think keeping DE & IT translation of the outdated doc is good. Let's say an italian want to read the doc as soon as he'll see the message about the doc probably outdated I think it'll go and check the english one.

Why bother reading the italian deprecated one while the english is up to date? 🤔

@j0k3r

This comment has been minimized.

Copy link
Member

commented Jun 5, 2019

I'm even thinking about removing the french documentation too.
It'll be less time consuming to translate the doc and it'll be faster for us to maintain it.

What do you think @wallabag/core ?

@tcitworld

This comment has been minimized.

Copy link
Member

commented Jun 5, 2019

I would vote to keep them at least in this repo but make https://doc.wallabag.org/ redirect directly to https://doc.wallabag.org/en/.

Below the The documentation is available in other languages: line, we should add a big warning that it's not updated for other languages.

@matteocoder

This comment has been minimized.

Copy link
Contributor

commented Jul 8, 2019

Long time no see guys! Unfortunately I don't have time to work on the Italian documentation at the moment, so please remove it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.