Talk:Plasma/Plasmoids

Jump to: navigation, search

Contents

Thread titleRepliesLast modified
2 bad links in Gmail plasmoid for images 605:05, 3 September 2018

2 bad links in Gmail plasmoid for images

Unknown URL -> Please correct , remove, or substitue. Thank you.

GOOGLE 404. That’s an error. The requested URL /svn/wiki/images/screenshots/notification.png was not found on this server. That’s all we know.

The requested URL /svn/wiki/images/screenshots/accountlist.png was not found on this server. That’s all we know.

11:57, 28 August 2018

http://gmail-plasmoid.googlecode.com/svn/wiki/images/screenshots/notification.png

The site googlecode is "closed since January, 26 2016 "

12:03, 28 August 2018

This whole page is in need of an update. I'll try to find info on the gmail plasmoid. I suspect it is obsolete.

04:55, 29 August 2018

I try to complete pages with a started translation but it is difficult to know that the page may be obsolete ; if there is a doubt , the EN pages should not be marked 'to be translated' ... but it is not easy to solve.

13:11, 29 August 2018

I agree. I do translations myself, and this is a problem. Unfortunately there is no obvious solution. I don't think that we can remove a page from the translation system once it has been added (other than possibly by deleting existing translations, which might create even more problems).

We could create a Category for such pages, but that would only be useful if we remember to check that a page is not in this no-translate category before starting to work on it. Do you think it would be a good idea to do that?

07:43, 2 September 2018

Hi Claus, Thanks for having answered. I would avoid multiplicity of categories. When one translates, it moves generally all categories from the EN page to the translated page (that is the local one) which at this second level becomes a nonsense (i have seen cases 'this category is only for the main/EN page' and I was attempting to recopy it on the FR page!).
If you know -thanks to your experience- that a page is obviously not good, i would rather recommend you to write a warning/comment at the top of the main/EN pages saying something like "Do not translate yet ! this page is too old and needs to be reactualized before being valid for translation." without requiring translation. Thus the process is locked at the level of the EN page. And when I check the FR pages to be translated, I dont see in the statistics this page which is still waiting for validation, because I am aligned with the old version. For translators it is better i think. No ?

10:51, 2 September 2018
 
 
 
 
 

This page was last edited on 28 August 2018, at 11:57. Content is available under Creative Commons License SA 4.0 unless otherwise noted.