Re: Smarty documentation translation - need some help

Hey Antony, thanks for the quick reply. I converted files to UTF-8 and changed encoding in XML declarations. I also changed configure.in to user UTF-8 instead of windows-1251 for Russian. After that everything worked like a charm! I'm not sure it is a good idea to commit it right away, as It can possibly break build in some way I haven't discovered yet. I'm CC'ing Monte so he knew what's going on. Here's the diff of configure.in: --- configure.in 21 Apr 2007 12:07:02 -0000 1.15 +++ configure.in 19 Jan 2008 15:47:26 -0000 @@ -346,7 +346,7 @@ AC_SUBST(BUILD_DATE) case "$LANG" in - ru) ENCODING="windows-1251" + ru) ENCODING="utf-8" FOP="$FOP -c fop/ru.cfg";; ja) ENCODING="utf-8";; *) ENCODING="ISO-8859-1";; The rest of the changes is inside "ru", but the diff is obviously too big to attach here. Monte, could you please approve or comment on this? Best regards, Georgiy Miroshnikov On Jan 19, 2008 3:41 PM, Antony Dovgal <tony@daylessday.org> wrote: > On 19.01.2008 16:33, Georgiy Miroshnikov wrote: > > I attached "preface.html" as an example. > > Uhm. Either you didn't or your attachment was stripped by the list engine > (which strips all non-text attachments). > > > The point is that Russian translation of Smarty docs are currently in > > windows-1251 as Smarty docs have not yet switched to UTF-8. > > I tried to tweak Makefile to add extra parameters but for no good. > > I'd start with converting it to UTF8 then, it's good idea even if it > doesn't fix the issue. > > > Just for a test, I tried to build Russian translation of PHP > documentation > > itself, which failed with a bunch of undefined entity errors. > > The docs are currently broken (because of overall update). > I'm working on it. > > -- > Wbr, > Antony Dovgal > > -- > PHP Russian Documentation Mailing List (http://php.net/manual/ru/) > To unsubscribe, visit: http://www.php.net/unsub.php > >