[wp-polyglots] Locale Directory Structure

K Suominen ksuominen at gmail.com
Mon Mar 7 02:03:05 GMT 2005


I'm not sure I understand what the benefit was from this, Morgan.  We
don't have a centralized packaging system yet, as far as I can tell,
so there was no need to do this unilaterally without consulting with
me.

The only result from the "re-organizaition" is that the tools I
contributed no longer work, and my own automation between my CVS repo
and the SVN repo is broken.

I tend to think I'm a reasonable person who can work together with
other people.  I don't find the "Kim, you'll have to update your
makefiles" a co-operative approach.  Any particular reason why you
decided there should be no discussion with me, the maintainer of that
part of the repository?

Regards,
+ Kim


On Mon, 28 Feb 2005 02:54:38 -0800, Morgan Doocy <morgan at doocy.net> wrote:
> fi_FI and ja_JP have been updated in the repository to reflect these
> conventions.
> 
> ja_JP's encoding names have been changed from EUC and UTF to EUC-JP and
> UTF-8. I also removed the svn:execute property from the message files.
> 
> In fi_FI, the contents of the /dist directory have been updated to
> reflect the directory structure convention, and put inside an
> ISO-8859-1 folder. The default theme folder is now inside an ISO-8859-1
> folder as well, and the message files have been renamed with ISO-8859-1
> in them. Kim, you'll have to update your makefiles to reflect these
> changes.
> 
> Morgan
> 
> On Feb 27, 2005, at 8:34 PM, Ryan Boren wrote:
> 
> > In order to make automated packaging easier, let's define the locale
> > directory structure more precisely.
> >
> > All trunk development happens under lc_CC/trunk/.  Beneath this we have
> > the following arrangement (using fr_FR as an example):
> >
> > ./fr_FR/trunk/dist:
> > license.txt  readme.html
> >
> > ./fr_FR/trunk/messages:
> > fr_FR.mo  fr_FR.po
> >
> > ./fr_FR/trunk/theme:
> > 404.php       comments-popup.php  index.php       search.php
> > archive.php   footer.php          links.php       sidebar.php
> > archives.php  header.php          page.php        single.php
> > comments.php  images              searchform.php  style.css
> >
> > ./fr_FR/trunk/theme/images:
> > kubrickbgcolor.jpg  kubrickbgwide.jpg  kubrickheader.jpg
> > kubrickbg.jpg       kubrickfooter.jpg
> >
> >
> > Consider the dist directory to be the root of a wordpress installation.
> > There is no need for a dist/wordpress/ subdirectory.  The dist
> > directory
> > will typically contain license.txt, readme.html, and
> > wp-config-sample.php.  If you put other WP files in there, please place
> > them in a directory structure that corresponds to the core WP
> > structure.
> > For example, wp-admin/install.php should go in
> > dist/wp-admin/install.php.  By the way, including wp-config-sample.php
> > is not necessary if you are just setting WPLANG.  That can be
> > automated.
> > If you want to localize the example username and password and the
> > comments, then including wp-config-sample.php is necessary.
> >
> > I notice that some locales are providing different versions of the
> > default theme for each character set they support.  Let's decide on a
> > structure for this.  How about:
> >
> > lc_CC/trunk/theme/UTF-8/index.php
> > lc_CC/trunk/theme/ISO-8859-1/index.php
> >
> > The character set name must match the name used for the po and mo
> > files.
> >
> > lc_CC.UTF-8.mo
> > lc_CC.ISO-8859-1.mo
> >
> > Also, let's use standard character set names.
> >
> > http://www.iana.org/assignments/character-sets
> >
> > For example, UTF-8 is not UTF or Unicode.  There is no such thing as
> > UTF, and Unicode is a set of code tables, not a specific character
> > encoding.
> >
> > http://www.cl.cam.ac.uk/~mgk25/unicode.html#utf-8
> >
> > If a character set is not specified, UTF-8 is assumed.
> >
> > Ryan
> >
> > _______________________________________________
> > wp-polyglots mailing list
> > wp-polyglots at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-polyglots
> 
> _______________________________________________
> wp-polyglots mailing list
> wp-polyglots at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-polyglots
>


More information about the wp-polyglots mailing list