Just shooting out a quick thought before I forget again -- it would be helpful in a number of places to be able to reference "internal" software-provided images from wikitext.
A primary example is for help pages and inline explanatory text in parts of the UI which we want to be able to customize. This is something that's coming up a lot in things the Usability crew is working on -- folding the wiki markup cheat sheet into mini-help pages accessible from the editor, having screen shots for skins and features so users can see what things are about before enabling them, etc.
One "simple" implementation could be to slip in a custom FileRepo, so they could be referred to just like other images:
[[Image:help-markup-example-thumbnail.jpg]]
To be slightly more complex, we could give them a unique sub-namespace of some sort, or strip out hardcoded extensions so that types can be more flexible.
Skins might want/need to be able to override certain names, too... and we might consider about needs for localized images -- whether RTL/LTR only or actually making translations available.
Any thoughts?
-- brion
On Tue, Jun 30, 2009 at 2:09 PM, Brion Vibberbrion@wikimedia.org wrote:
Just shooting out a quick thought before I forget again -- it would be helpful in a number of places to be able to reference "internal" software-provided images from wikitext.
A primary example is for help pages and inline explanatory text in parts of the UI which we want to be able to customize. This is something that's coming up a lot in things the Usability crew is working on -- folding the wiki markup cheat sheet into mini-help pages accessible from the editor, having screen shots for skins and features so users can see what things are about before enabling them, etc.
One "simple" implementation could be to slip in a custom FileRepo, so they could be referred to just like other images:
[[Image:help-markup-example-thumbnail.jpg]]
To be slightly more complex, we could give them a unique sub-namespace of some sort, or strip out hardcoded extensions so that types can be more flexible.
Skins might want/need to be able to override certain names, too... and we might consider about needs for localized images -- whether RTL/LTR only or actually making translations available.
Any thoughts?
-- brion
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
A built-in FileRepo would be nice. Pretty straightforward to implement, wouldn't require any major changes to put in place. We could easily put some standard descriptions into the i18n files and load those for the page's info.
Make sure to place it higher in the priority than any custom-defined remote repos, or we'll end up loading the remote repo's images that we already have locally.
-Chad
Hoi. At the Open Translation Tools conference last week we talked about pictures and icons in a user interface. I learned that some of the "obvious" symbols like a magnifying glass are not appropriate in other cultures. So I am completely in favour of integrating images in the UI but PLEASE allow for internationalisation and the corresponding localisation to remove images when there is a need. Thanks, GerardM
2009/6/30 Brion Vibber brion@wikimedia.org
Just shooting out a quick thought before I forget again -- it would be helpful in a number of places to be able to reference "internal" software-provided images from wikitext.
A primary example is for help pages and inline explanatory text in parts of the UI which we want to be able to customize. This is something that's coming up a lot in things the Usability crew is working on -- folding the wiki markup cheat sheet into mini-help pages accessible from the editor, having screen shots for skins and features so users can see what things are about before enabling them, etc.
One "simple" implementation could be to slip in a custom FileRepo, so they could be referred to just like other images:
[[Image:help-markup-example-thumbnail.jpg]]
To be slightly more complex, we could give them a unique sub-namespace of some sort, or strip out hardcoded extensions so that types can be more flexible.
Skins might want/need to be able to override certain names, too... and we might consider about needs for localized images -- whether RTL/LTR only or actually making translations available.
Any thoughts?
-- brion
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hoi, The operational word is replace not remove. Thanks, Gerard
2009/6/30 Gerard Meijssen gerard.meijssen@gmail.com
Hoi. At the Open Translation Tools conference last week we talked about pictures and icons in a user interface. I learned that some of the "obvious" symbols like a magnifying glass are not appropriate in other cultures. So I am completely in favour of integrating images in the UI but PLEASE allow for internationalisation and the corresponding localisation to remove images when there is a need. Thanks, GerardM
2009/6/30 Brion Vibber brion@wikimedia.org
Just shooting out a quick thought before I forget again -- it would be
helpful in a number of places to be able to reference "internal" software-provided images from wikitext.
A primary example is for help pages and inline explanatory text in parts of the UI which we want to be able to customize. This is something that's coming up a lot in things the Usability crew is working on -- folding the wiki markup cheat sheet into mini-help pages accessible from the editor, having screen shots for skins and features so users can see what things are about before enabling them, etc.
One "simple" implementation could be to slip in a custom FileRepo, so they could be referred to just like other images:
[[Image:help-markup-example-thumbnail.jpg]]
To be slightly more complex, we could give them a unique sub-namespace of some sort, or strip out hardcoded extensions so that types can be more flexible.
Skins might want/need to be able to override certain names, too... and we might consider about needs for localized images -- whether RTL/LTR only or actually making translations available.
Any thoughts?
-- brion
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Tue, Jun 30, 2009 at 2:36 PM, Gerard Meijssengerard.meijssen@gmail.com wrote:
Hoi, The operational word is replace not remove. Thanks, Gerard
2009/6/30 Gerard Meijssen gerard.meijssen@gmail.com
Hoi. At the Open Translation Tools conference last week we talked about pictures and icons in a user interface. I learned that some of the "obvious" symbols like a magnifying glass are not appropriate in other cultures. So I am completely in favour of integrating images in the UI but PLEASE allow for internationalisation and the corresponding localisation to remove images when there is a need. Thanks, GerardM
2009/6/30 Brion Vibber brion@wikimedia.org
Just shooting out a quick thought before I forget again -- it would be
helpful in a number of places to be able to reference "internal" software-provided images from wikitext.
A primary example is for help pages and inline explanatory text in parts of the UI which we want to be able to customize. This is something that's coming up a lot in things the Usability crew is working on -- folding the wiki markup cheat sheet into mini-help pages accessible from the editor, having screen shots for skins and features so users can see what things are about before enabling them, etc.
One "simple" implementation could be to slip in a custom FileRepo, so they could be referred to just like other images:
[[Image:help-markup-example-thumbnail.jpg]]
To be slightly more complex, we could give them a unique sub-namespace of some sort, or strip out hardcoded extensions so that types can be more flexible.
Skins might want/need to be able to override certain names, too... and we might consider about needs for localized images -- whether RTL/LTR only or actually making translations available.
Any thoughts?
-- brion
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
This is very true. I don't see any reason why the file repo designed around this cannot handle such scenarios. Either that, or the Language classes a way to load localized images when needed (which the file repo could easily sit on top of)
-Chad
2009/6/30 Brion Vibber brion@wikimedia.org:
Skins might want/need to be able to override certain names, too... and we might consider about needs for localized images -- whether RTL/LTR only or actually making translations available.
Like http://laxstrom.name/blag/2008/07/05/localisation-of-images/ ? Or was the question about how to refer to those alternatives in wiki syntax?
wikitech-l@lists.wikimedia.org