Jump to content

wayne

Members
  • Posts

    26
  • Joined

  • Last visited

Posts posted by wayne

  1. I haven't checked yet, but maybe the T in "Tag" gets replaced by the translated tense variable, like it's done in "T Q P".

    EDIT:

    I think it's the following line:

    $out = str_replace(array('Q', 'P', 'T'), array(" $quantity", " $period", " $tense"), $format); 
    

    str_replace replaces Q, P and T one after the other. In the second round P gets replaced by the content of $period ("Tag"), that "T" also gets replaced by the content of $tense in the last round.

    A solution may be to use prefixes, that wouldn't appear in a translation, like "%Q".

    EDIT 2:

    Btw ryan, you already pushed that change to github with your last update to ProcessModule. I think this wasn't intended.

  2. In theory there shouldn't be such a big problem with fonts on the latest Chrome for Windows, if DirectWrite is enabled.

    It's not an experimental feature anymore. Under the URL "chrome://flags/" DirectWrite should be activated.

    Maybe there are still some quirks, but for me it looks quite similar or even identical to IE and FF.

  3. I'm starting this topic for a problem I see with the German translations of relative times. But other languages may be affected as well.

    You can see the problem when the Lister module shows a column with a past date.

    In English it says "3 years ago" and in German it's translated to "3 Jahre vor". But it really should be "vor 3 Jahren".

    The phrase is constructed with the single translations of "years" and "ago" in the same order as it is in English.

    So the problem is about grammar and word order in the German translation.

    Maybe it could be solved by a list of translatable phrases with placeholders, so that it looks like "%d years ago" or in German "vor %d Jahren". That is just a quick thought and it probably should be discussed here before it is posted as an issue on github.

    • Like 5
  4. new german updates for actual PW dev 2.4.4 (12 June 2014).

    Zip contains only updated/added files (in comparison to the default 2.4 lang pack).

    updated files:

    wire--templates-admin--default-php.json

    wire--modules--fieldtype--fieldtypepagetable-module.json

    wire--modules--system--systemupdater--systemupdater-module.json

    added files:

    wire--modules--process--processpagelister--processpagelister-module.json

    attachicon.gifpw-lang-de-dev-update.zip

    It's really great, that you keep it up to date with the dev version.

    I have also found another file that needs translation for the new Lister module:

    /wire/modules/Inputfield/InputfieldSelector/InputfieldSelector.module

    This seems to contain the phrases for the filter dropdowns.

    • Like 1
  5. I would also recommend to reset the password.

    And here is an additional explanation:

    Depending on the host's PHP version processwire uses the strongest available blowfish algorithm.

    So all passwords become "invalid" if the password algorithm changes.

    For example if your remote PHP version is above 5.3.7 and your local version is below that, processwire generates different password hashes.

    There could be other conditions for differing password hashes, but basically it's that.

    • Like 3
  6. That's definitely a clean and modern webdesign. A set of photos from a professional photoshooting can really boost every webdesign.

    I wish I could convince more of my clients to invest in one.

    There's one small thing I would criticize. It's the small space (or contrast) between the main content and the right address column.

    On some pages with a lot of text it kind of disturbs my reading flow (as my eyes are wandering to the similar looking text in the right column).

    I'm not a professional webdesigner, so that's an absolute personal opinion.  :undecided:

    All in all the photos, minimal design elements and the content work great together.

    • Like 1
  7. I'm not sure. From what he told me I can only imagine that he had some kind of blackout.

    Somehow his actions led him to the delete tab and he thought that he should confirm the deletion of the picture there.

    I can't comprehend that but you know there is always a special kind of users out there,

    like those managing to format their harddrives and being clueless afterwards (=> wth just happened).

  8. My client of the day had a little problem with handling Processwire.

    He just wanted to delete a picture on a page but he ended up on deleting the whole page and it's sub pages.

    All glory to the trash and the ability to restore pages.

    Not so long and I will have to install teppo's version control module solely as precaution for "accidentally" deleted content.

    • Like 2
  9. the translation for the headings under Setup and Access is broken

    Like I said before, the use of / and \ is quite inconsistent. I guess that condition should check for both kinds of slashes under Windows.

    Could you try to change

    if(is_string($textdomain) && strpos($textdomain, DIRECTORY_SEPARATOR) !== false) $textdomain = $this->filenameToTextdomain($textdomain);
    

    to

    if(is_string($textdomain) && (strpos($textdomain, DIRECTORY_SEPARATOR) !== false || strpos($textdomain, '/') !== false)) $textdomain = $this->filenameToTextdomain($textdomain);
    

    ?

    EDIT:

    I tested it, and that works (at least for me).

  10. Hi Radek,

    the Czech language pack isn't working just like the German one.

    Thanks for pointing to the environment, I will have a look at my setup.

    EDIT:

    I found the problem. It's the Windows environment and it's backslash pathes.

    PW uses the DIRECTORY_SEPARATOR constant in its php code that is a backslash character under Windows.

    Basically this is correct. But php isn't quite consistent in that matter.

    The translation function gets pathes with normal slashes although the code uses backslashes because of the DIRECTORY_SEPARATOR constant.

    The only function that seems to cause that problem is in "wire/modules/LanguageSupport/Languagetranslator.php":

    	protected function textdomainString($textdomain) {
    
    		if(is_string($textdomain) && strpos($textdomain, DIRECTORY_SEPARATOR) !== false) $textdomain = $this->filenameToTextdomain($textdomain); 
    			else if(is_object($textdomain)) $textdomain = $this->objectToTextdomain($textdomain); 
    			else $textdomain = strtolower($textdomain); 
    
    		// just in case there is an extension on it, remove it 
    		if(strpos($textdomain, '.')) $textdomain = basename($textdomain, '.json'); 
    
    		return $textdomain;
    	}
    

    If you replace DIRECTORY_SEPARATOR with a simple '/', it works.

    (EDIT3: That change isn't enough, look at the posts below.)

    I don't know if there is a clean solution or if one should write it off as a Windows php quirk.

    A quick and dirty fix would be to check for a backslash and a normal slash as directory separator.

    EDIT2:

    In the subroutine "filenameToTextdomain" I found an existing directory separator fix:

    if(DIRECTORY_SEPARATOR != '/') $filename = str_replace(DIRECTORY_SEPARATOR, '/', $filename); 
    

    But for the problem explained above it comes one subroutine to late.

    I think it's now on Ryan to decide where and how to fix that check for the DIRECTORY_SEPARATOR in the "textdomainString" function.

    • Like 3
  11. To make it short:

    - I downloaded the latest German language pack from github and installed it

    - default.php from AdminTheme module suggests to translate "/wire/templates-admin/default.php" and I checked, it already is

    - everything but the admin/backend menu and breadcrumbs is translated

    Did I miss or oversee something?

  12. But essentially, this site involves 1 PW installation for managing the inventory, and another PW installation for presenting it, and they use web services to chat back and forth all day. 

    I'm also quite interested in the concept behind those two PW installations.

    And of course: Great job on that.

    Did the client say anything about IE compatibility?

  13. I think the same way. It was interesting to see which problems can arise by the use of font face, but it's not worth the effort for a backend.

    A CMS backend is just supposed to be a management platform and nothing more.

    Just focus on elements for the admin theme that make it more usable and clearer.

    Maybe it's best to follow Martijn's suggestion, especially if the theme is responsive.

    In my eyes a webfont is only useful for serious design purposes or to get the same font appearance across different platforms and browsers. But as we learned, this isn't possible because of those different rendering techniques.

    Besides here is a font stack of similar fonts from best to worst:

    font-family: "Helvetica Neue", "Liberation Sans", Arimo, Helvetica, Arial, sans-serif;

    It's useless if those fonts are the preconfigured sans-serif fonts anyway.

  14. I can confirm that the new font size improves the rendering of bold Arimo text. (Windows 7)

    At the moment "text-stroke" is only available in Webkit browsers and it's too much about experimenting with values for my taste.

    I would advise against the overuse of such css properties. Don't try to solve something here that the rest of the webdesign community couldn't solve yet.

  15. the difference is minimal on Win 7, 64bit. First is Firefox, second is Chrome (both actual versions). Safari 5.1.7 on Win 7 looks the same like Chrome.

    attachicon.gifpw-arimo-fx.jpg attachicon.gifpw-arimo-chrome.jpg

    Your second screenshot shows the same distorted "e" in "Seiten" I get with my Firefox and Chrome.

    I don't know why your Firefox renders it differently compared to mine.

    However one thing that messes this up is definitely Window's ClearType.

    Turn it off and particular the Arimo font looks partly better but also partly worse (in Windows Chrome browser).

    By no means turn off ClearType permanently. But this proves that there is an annoying flaw in Window's own smoothing algorithm.

    I couldn't find any solution yet.

    Some people suggest using FontSquirrel's webfont generator but the results still look quite ugly.

    EDIT:

    Ok, I found out that the different rendering in Manfred's Firefox is the result of hardware acceleration.

    My acceleration option is turned off because of some graphics card bugs, but If you turn it on Firefox uses DirectWrite for font rendering.

    DirectWrite + ClearType does a bit better job than GDI + ClearType.

    • Like 1
×
×
  • Create New...