[kdewebdev-site] kdewebdev.org proposals

[David Joham]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 27 April 2004 04:48 am, Chris Hornbaker wrote:

>
> It can be done right now. :-D
>
> xgettext
> bash
> perl
>

OK. Pretend I'm a new user (easy, since I am in regards to localization). 
Let's go through what you just outlined....


xgettext: no input file given
Try `xgettext --help' for more information.

Huh? Well, OK.....

xgettext --help
Usage: xgettext [OPTION] [INPUTFILE]...

Extract translatable strings from given input files.

Mandatory arguments to long options are mandatory for short options too.
Similarly for optional arguments.

Input file location:
  INPUTFILE ...               input files
  -f, --files-from=FILE       get list of input files from FILE
  -D, --directory=DIRECTORY   add DIRECTORY to list for input files search
If input file is -, standard input is read.

Output file location:
  -d, --default-domain=NAME   use NAME.po for output (instead of messages.po)
  -o, --output=FILE           write output to specified file
  -p, --output-dir=DIR        output files will be placed in directory DIR
If output file is -, output is written to standard output.

Choice of input file language:
  -L, --language=NAME         recognise the specified language
                                (C, C++, ObjectiveC, PO, Shell, Python, Lisp,
                                EmacsLisp, librep, Smalltalk, Java,
                                JavaProperties, awk, YCP, Tcl, Perl, PHP,
                                GCC-source, NXStringTable, RST, Glade)
  -C, --c++                   shorthand for --language=C++

<lengthy programmer-speak gibberish clipped>
...


Uhm. OK :) Now what?

Let's move on to Bash. Bash what? With what? An oyster? Do I Bash the oyster 
to get the Perl? I get it! Don't I?


:)


My rather long-winded point is that we *have* to make this easy for people who 
only know web development. D. Reddish's proposal does that (I still don't 
know your first name D :) - but I'm concerned about a lack of content 
separation in his proposal...

I'm not dissing you Chris - quite the opposite. I'm challenging you to prove 
to me that what you're proposing is easy for someone with web development 
skills but no KDE development experience.


I'd also like to ask a question of both you and D Reddish. At HP, we have a 
simple table structure layed out like the following...

| Localization ID               | English Text  | Klingon Text | .....
- -----------------------------------------------------------------------------------------------------
|  locIDShuttlecraft          | Shuttlecraft   | lupDujHom  | ....

*http://www.amazon.com/gp/reader/0671543490/ref=sib_rdr_next1_2/002-0008525-0958475?%5Fencoding=UTF8&p=S00B&ns=1#reader-page

And when we want some text, we (in a nutshell) call something like 

String locString = locSubsystem.getL10NString(locIDShuttlecraft);


I'm not predisposed to this solution, but I do find it simple and fairly easy 
to work with. I'm curious if either of you considered it and if so, why you 
decided it was not worth pursuing? Is it a PHP vs. Java thing?



David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAjxIFdGtRHnP4AioRAgeDAJ4pRbfeuTGVkrBhmg5zhkLsoyf1tgCgtlie
TuQlx7SF8JWe0SwNclKkJ1c=
=RY3e
-----END PGP SIGNATURE-----