On Thu, Apr 19, 2012 at 2:27 PM, Burkhard L?ck <lueck at hube-lueck.de> wrote: > Am Montag, 6. Februar 2012, 05:57:11 schrieb T.C. Hollingsworth: >> >> Otherwise, I'm going to get started on the visual dictionary here pretty >> soon. >> > Would be great to add that for consistent wording in docs/translation.
I can get started on this soon. >> > Thinking about the module where to commit I changed my mind and propose >> > to go with kde-runtime module for these reasons: >> > >> > * we can't commit to kdelibs master, it is frozen. But we need a >> > roundtrip for the docs in trunk for translators >> > >> > * I don't know how kdelibs/doc + kdelibs/kdoctools master will be/is >> > changed or splitted in frameworks branch and would like to keep the >> > buildingblocks out of that trouble >> > >> > * in kde-runtime we can have a scripty roundtrip in master and later >> > backport a tested/corrected version without trouble for the translation >> > teams. >> > >> > Before we push the building blocks to master we should announce the >> > purpose on the translators list and encourage them them for feedback and >> > to send comments about missing/wrong info they found while translating >> > to this list. >> > T.C, please push to master kde-runtime, I need the building blocks already > for: > > * Lokalize link to shortcut/toolbar configuration > > * krecipes to replace outdated kde3 stuff (shortcut/toolbar configuration) > with > a link to building blocks > > * kcolorchooser link to buildingblocks. > > What Name should we use for d.k.o and KHelpcenter? > > "KDE Basics" ? > > Any better name? I have "KDE Fundamentals" in <title> right now. Either one works for me. Should I keep buildingblocks as the directory name or use something else? > Thanks. -T.C.
